Download JAR files tagged by transitive with all dependencies

Enforces our invariants for the api and runtime client modules. E.g. that modules have a specific set of transitive dependencies and shaded artifacts only contain classes that are in particular packages. Does the enforcement through the maven-enforcer-plugin and an integration test.

Enforces our invariants for our shaded artifacts. e.g. shaded clients have a specific set of transitive dependencies and shaded clients only contain classes that are in particular packages. Does the enforcement through the maven-enforcer-plugin and and integration test.

Defines different categories (SlowTests, FastTests, ...) we can specify for unit testing. Added as test dependency, otherwise we cannot specify the category in aggregator builds / on top level. This serves also as a test scope BOM for transitive dependencies to JUnit and hamcrest.

The top level API module for NoSQLBench. This module should have no internal module dependencies other than the mvn-default module. All modules within NoSQLBench can safely depend on this module with circular dependencies. This module provides cross-cutting code infrastracture, such as path utilities and ways of describing services used between modules. It is also the transitive aggregation point for system-wide library dependencies for logging and testing or similar needs.

Switchgear is a Java library that provides an API for call isolation, timeouts, and circuit breaker functionality. Our main goal is to achieve minimal performance overhead of the library, even when used in the hottest place of your application. Additionally, we've opted for zero transitive dependencies and maintaining a fluent API.

The maven-dependency-versions-check-plugin is a Maven plugin that verifies that the resolved versions of dependencies are at least the versions specified by the dependencies (or their dependencies etc.) if not higher. More specifically, it will check that * The resolved version of every dependency declared explicitly in the current POM is the same or a newer one than what was stated. If the resolved version has a higher major version number than the declared version, then the plugin will issue a warning if configured to do so. Note that enforced declared versions are ignored by the plugin. * For every explicitly declared dependency in the current POM, all its dependency versions are met. I.e. the resolved versions for all dependencies in that dependency's POM are the same or higher than the one stated in that dependency's POM. This is basically the same check as the one above, but using the dependency's POM! Also, if the current POM has exclusions specified for the dependency, then these transitive dependencies are ignored when checking this particular dependency.

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

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

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.