Download JAR files tagged by avoid with all dependencies

This module was created to fix issue DIRSHARED-91 where the embedded Felix instance inside the default LdapCodecService implementation was making it very problematic to deploy the ldap-codec inside an RCP (OSGi) environment and hence Apache Directory Studio could not use it. This module is most likely temporary and will disappear once we are fully OSGi enabled. This module is a plain old jar, not a bundle to avoid accidental reuse as an OSGi module because it contains the version of the LdapCodecService that embeds Felix to make controls and extended ops pluggable in the codec.

Provides non-free data, including the EPSG geodetic dataset, in a single read-only JAR file. This 'sis-embedded-data' module contains a copy of EPSG geodetic dataset in an embedded Apache Derby database. Having this module on the classpath avoid the need to set the 'SIS_DATA' environment variable for using the Coordinate Reference Systems (CRS) and Coordinate Operations defined by EPSG. EPSG is maintained by the IOGP Surveying & Positioning Committee and reproduced in this module with same content. See https://www.epsg.org/ for more information.

This project is a library for any POJO class to implement a toString method. Given a class name and instance, the project will use reflection from Java API to get the getter methods for the given instance and execute it to print the methodName = methodValue in an appended string with comma separated values. This is very generic implementation so anybody can use this code to write their toString implementation. The idea is to avoid implementing toString by writing your own implementation every time. Please put your thoughts on the implementation so we can evolve as a project which will help every Java Developer.

Burningwave core is an advanced, free and open source Java library that contains THE MOST POWERFUL CLASSPATH SCANNER for criteria based classes search. It’s possible to search classes by every criteria that your immagination can made by using lambda expressions. Burningwave core scan engine is highly optimized using direct allocated ByteBuffers to avoid heap saturation; searches are executed in multithreading context and are not affected by “the issue of the same class loaded by different classloaders” (normally if you try to execute "isAssignableFrom" method on a same class loaded from different classloader it return false). This library is useful also for creating classes during runtime, facilitate the use of reflection and much more...

This module packages a circuit breaker that can be used to avoid overloading or otherwise depending on a temporarily unavailable (remote) system. The central use of the circuit breaker is to prevent failures from one system to cascade to other systems in an unchecked manner. Thus, our implementation is chiefly concerned with replacing a failing component with another component that fails in a very predictable manner. These failures are not "dropped" or otherwise made invisible, and still need to be handled, but they will occur in a predictable, and hopefully usable manner.

An empty artifact that Guava depends on to signal that it is providing ListenableFuture -- but is also available in a second "version" that contains com.google.common.util.concurrent.ListenableFuture class, without any other Guava classes. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... version number is enough for some build systems (notably, Gradle) to select that empty artifact over the "real" listenablefuture-1.0 -- avoiding a conflict with the copy of ListenableFuture in guava itself. If users are using an older version of Guava or a build system other than Gradle, they may see class conflicts. If so, they can solve them by manually excluding the listenablefuture artifact or manually forcing their build systems to use 9999.0-....

--------------------------------------------------------------------------- Version for VIVO 1.9 This uses the source and test code from the Version for VIVO 1.10, edited to make it compatible with VIVO 1.9. It also borrows some code from VIVO 1.10 itself, changes the package name to avoid conflicts, and adds it here. * Vitro 1.9 uses Jena 2, not Jena 3, and Commons Lang 2, not 3, so modify the "import" statements in the Data Distribution code accordingly. * Vitro 1.9 has an earlier version of "...webapp.utils.sparqlrunner" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this sparqlrunner package. * Vitro 1.9 has an earlier version of "...webapp.utils.configuration" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this configuration package. Make these modifications, compile, JAR it up, and deploy. ---------------------------------------------------------------------------