Download JAR files tagged by could with all dependencies

This bill of materials (BOM) POM covers all the Apache HttpClient artifacts related to a particular version. By importing this BOM, you fix the version of all of HttpClient-related artifacts to the versions associated with a particular release. This prevents the overriding of HttpClient 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>httpclient-bom</artifactId> <version>4.3.2</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> And then declare your dependency on the HttpClient artifacts *without* a version.

This bill of materials (BOM) POM covers all the Hibernate ORM artifacts related to a particular version. By importing this BOM, you fix the version of all of Hibernate-related artifacts to the versions associated with a particular release. This prevents the overriding of Hibernate 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>hibernate-orm-bom</artifactId> <version>4.3.1.Final</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> And then declare your dependency on the Hibernate artifacts *without* a version.

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.

The Sakai Wicket Maven Archetype allows you to generate a sample Sakai app via a single Maven command. The app is based on Apache Wicket which integrates nicely with Sakai. The app demonstrates how to get a Sakai tool styled, internationalised and registered, setup your own APIs, wire them up with Spring and inject them via annotations. The 1.1 and up releases also include multi database support via Spring JDBC. It could easily be used as a base for a real tool.

The framework library contains utility classes that are generic and useful for building applications that introspect a database via JDBC. These are not intended to be SQuirreLSQL-specific and could be used by other projects JDBC front-end applications. This project is guaranteed to have no code dependencies on other SQuirreLSQL projects and could therefore be used when building a different JDBC front-end application.

Several kinds of two column key/value data structures, in memory and on disk which sort keys can can be used to implement xdbm partitions. JDBM is one example. These partition use the same database structure or scheme for maintaining LDAP entries and facilitating search operations on them. This module contains common tools that could be used to manage aspects common to all xdbm implementations.

This plugin creates a server specific repository (var/repository) for a Geronimo server instance. This server repository can be used to provide some isolation from the default Geronmio repository and is of most value with multiple server instances leveraging the same Geronimo install image. For a description of how this could be used see http://cwiki.apache.org/GMOxDOC21/multiple-repositories.html

Evita is a specialized database with easy-to-use API for e-commerce systems. Purpose of this research is creating fast and scalable engine that handles all complex tasks that e-commerce systems has to deal with on daily basis. Evita should operate as a fast secondary lookup / search index used by application frontends. We aim for order of magnitude better latency (10x faster or better) for common e-commerce tasks than other solutions based on SQL or NoSQL databases on the same hardware specification. Evita should not be used for storing and handling primary data, and we don't aim for ACID properties nor data corruption guarantees. Evita "index" must be treated as something that could be dropped any time and built up from scratch easily again.