Download JAR files tagged by cause with all dependencies

This artifact provides a single jar that contains all classes required to use remote Jakarta Enterprise Beans and Jakarta Messaging, including all dependencies. It is intended for use by those not using maven, maven users should just import the Jakarta Enterprise Beans and Jakarta Messaging BOM's instead (shaded JAR's cause lots of problems with maven, as it is very easy to inadvertently end up with different versions on classes on the class path).

This artifact provides a single jar that contains all classes required to use remote Jakarta Enterprise Beans and Jakarta Messaging, including all dependencies. It is intended for use by those not using maven, maven users should just import the Jakarta Enterprise Beans and Jakarta Messaging BOM's instead (shaded JAR's cause lots of problems with maven, as it is very easy to inadvertently end up with different versions on classes on the class path).

The filter plugs into the logging pipeline and measures number of log events at each trace level. These counters can be used to monitor error levels for the entire application and for individual loggers. The filter can be also configured to send a subset of log events into a backend storage system such as Axibase Time-Series Database to facilitate root-cause analysis.

The filter plugs into the logging pipeline and measures number of log events at each trace level. These counters can be used to monitor error levels for the entire application and for individual loggers. The filter can be also configured to send a subset of log events into a backend storage system such as Axibase Time-Series Database to facilitate root-cause analysis.

The filter plugs into the logging pipeline and measures number of log events at each trace level. These counters can be used to monitor error levels for the entire application and for individual loggers. The filter can be also configured to send a subset of log events into a backend storage system such as Axibase Time-Series Database to facilitate root-cause analysis.

The filter plugs into the logging pipeline and measures number of log events at each trace level. These counters can be used to monitor error levels for the entire application and for individual loggers. The filter can be also configured to send a subset of log events into a backend storage system such as Axibase Time-Series Database to facilitate root-cause analysis.

The filter plugs into the logging pipeline and measures number of log events at each trace level. These counters can be used to monitor error levels for the entire application and for individual loggers. The filter can be also configured to send a subset of log events into a backend storage system such as Axibase Time-Series Database to facilitate root-cause analysis.

Scott provides detailed failure messages for tests written in Java based on their runtime behaviour and source code. With Scott even simple assertions provide the details needed to trace the cause of the failure and to comprehend the context of the test case. It provides details about local variables to reduce the need to debug tests.

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.