Download JAR files tagged by associated with all dependencies

This bill of materials (BOM) POM covers all the AspectJ artifacts related to a particular version. By importing this BOM, you fix the version of all the AspectJ-related artifacts to the versions associated with a particular release. This prevents the overriding of AspectJ transitive dependencies which in turn could cause version conflicts between libraries. To use this BOM, add the following in your POM: <dependencyManagement> <dependencies> <dependency> <groupId>com.covisint.core</groupId> <artifactId>aspectj-bom</artifactId> <version>1.8.0</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> And then declare your dependency on the AspectJ artifacts *without* a version.

This bill of materials (BOM) POM covers all the Metrics artifacts related to a particular version. By importing this BOM, you fix the version of all of Metrics-related artifacts to the versions associated with a particular release. This prevents the overriding of Metrics transitive dependencies which in turn could cause version conflicts between libraries. To use this BOM, add the following in your POM: <dependencyManagement> <dependencies> <dependency> <groupId>com.covisint.core</groupId> <artifactId>metrics-bom</artifactId> <version>3.0.2</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> And then declare your dependency on the Metrics artifacts *without* a version.

API for stackable stateful encoders and decoders. Such codec interfaces allow for the efficient processing of data as it is made available while maintaining small actively processing footprints. Of course these aspects depend on the implementation as well however this API standardizes the minimum set of interfaces associated with codec's that are stateful. Until this API is added to the commons-codec project several interfaces and classes here are duplicated to minimize the number of dependencies: namely a dependency on commons-codec will be avoided.

The Plasma project is an SDO 2.1 implementation with associated provisioning and other tools. In its initial releases, the PlasmaSDO™ implementation seeks to address the need for automation and code generation under SDO for standard enterprise Java web applications while focusing on critical operational considerations these applications face, such as optimistic and pessimistic concurrency control. The PlasmaSDO™ implementation is not bound to any integrated development environment (IDE) and provides support for standard Java™ based build tools. Note: Such operational considerations such as optimistic and pessimistic concurrency control are seen as a feature gap within various commercial and open-source SDO offerings, and are facilitated in PlasmaSDO™ by a custom UML profile and various associated SDO API extensions.

With distributed systems being developed as a part of the cloud age. With focus on performance associated with an application dependent on one DB instance, there is a need to bring down the dependency to a database to generate unique numbers for creating a private key when lots of data needs to be stored in the database tables. This library is intended to provide a way of generating unique numbers on the fly in a JAVA based distributed system. This is not a new concept but this library helps in keeping you focused on the business logic that you need to develop for your applications rather than spending time on how this is done. Typically applications powered by RDBMS can leverage the benefit as instant scalability might not be available for these setups when the load to the system spikes.

The JSP TLD Maven Plugin is used to automate the management of JSP Tag Library Descriptors as part of a Maven build. It is intended to decrease the burden on JSP developers associated with writing custom JSP Tag Libraries. The goal is to encourage JSP developers to write better JSP files by using custom JSP Tag Libraries more extensively. The Plugin can process Java annotations on Tag implementation classes and also discover Tag Files (.tag and .tagx files). The Java 5 Annotations recognized by this Plugin are all part of the <a href="../squeakysand-jsp/apidocs/com/squeakysand/jsp/tagext/annotations/package-summary.html">com.squeakysand.jsp.tagext.annotations</a> package.

This subproject is an extension of the Struts tag library. Each JSP custom tag in this library is a subclass of an associated tag in the Struts tag library. One difference is that this tag library does not use "rtexprvalues", it uses the expression evaluation engine in the Jakarta Taglibs implementation of the JSP Standard Tag Library (version 1.0) to evaluate attribute values. In addition, some of the Struts tags were not ported to this library, as it was determined that their functionality was entirely supplied by the JSTL. These particular Struts tags, and the reason for their non-porting will be described in the documentation for this library. In order to fully understand the correct utilization of this library, you must understand the use and operation of the Struts tag library, and the use and operation of the JavaServer Pages Standard Tag Library (hereafter called the "JSTL"), along with the expression language (sometimes called the "EL") used for evaluating attribute values.

Apache Spatial Information System (SIS) is a free software, Java language library for developing geospatial applications. SIS provides data structures for geographic features and associated metadata along with methods to manipulate those data structures. The library is an implementation of GeoAPI 3.0.2 interfaces and can be used for desktop or server applications. The SIS metadata module forms the base of the library and enables the creation of metadata objects which comply with the ISO 19115 international standard. The SIS referencing module enable the construction of geodetic data structures for geospatial referencing as defined by ISO 19111 standard, along with the associated operations which enable the transformation of coordinates between different reference systems. The SIS storage modules provide a common approach to the reading and writing of metadata, features and coverages applicable to simple imagery as to many dimensional data structures.

MyDtt-Plus is a starter of spring-boot, It is an object-oriented Java framework that helps developers increase productivity, "Domain Driven Table" is the concept of DTT, It makes you focus more on domain objects rather than tables. Aims to make it easy to automatically create DB tables based on your Java model with annotation driven. It's also support the ability of create table automatically for MyBatis what Hibernate can do and optionally export SQL to local file，Each table can be added database name concat with table name and fully comments, It can work with ORM frameworks such as MyBatis-Plus and MyBatis with little learning and usage costs. It's worth mentioning that DTT can be MyBatis-Plus is integrated in a 0-code way, just like JPA. However, MyDtt-Plus and MyBatis-Plus may be easier to expand and use than JPA. In addition to supporting the functions of JPA, DDT provides multi-table associated SQL DDL based on MyBatis operation, DTT support databases server for MYSQL, ORACLE, DB2, SQLSERVER, MARIADB, POSTGRESQL and embedded database for H2, HSQL, DERBY.

The Liberty Audit feature is used to report and track auditable events to ensure the integrity of your system. The Liberty Audit feature introduces an infrastructure which serves two purposes: - Confirming the effectiveness and integrity of the existing configuration - Identifying areas where improvement to the configuration may be needed The Liberty Audit feature has the ability to capture the following auditable events: - Basic authentication - Start and stop of the Audit service - Form login - Client certificate login - Servlet runAs delegation - Form logout - Servlet 3.0 login, logout and authenticate APIs The Liberty Audit feature supports the Cloud Auditing Data Federation (CADF) event model. The CADF model describes a data model and associated schema definitions for an audit event. The feature provides a default implementation, the AuditFileHandler, which emits human-readable audit records to a file-based log. Each audit record is emitted in JSON format.