Download JAR files tagged by depends with all dependencies

Open and Free WSDL library: Web Services Description Language. Libre-wsdl4j is a fork of WSDL4J 1.6.3. WSL4j is a Java stub generator for WSDL. Many software projects still depends on WSL4j, so the idea is that libre-wsdl4j should be an actively maintained version of this software on GitHub. "WSDL, that's an anchronym i haven't heard in almost ten years." Still big in the enterprise world" - comments on the Internet.

AuthzForce PDP extensions for JSON value processing, in particular JSONPath evaluation; it provides the XACML datatype 'urn:ow2:authzforce:feature:pdp:datatype:json' for JSON object/array values, and XACML functions that evaluate a JSON path (second parameter of standard string datatype) against an input JSON object/array (first parameter of datatype 'urn:ow2:authzforce:feature:pdp:datatype:json') and return the result of this evaluation. The return datatype depends on the actual function used: 'urn:ow2:authzforce:feature:pdp:function:string-from-json-path' returns a bag of strings, 'urn:ow2:authzforce:feature:pdp:function:integer-from-json-path' returns a bag of integers, 'urn:ow2:authzforce:feature:pdp:function:double-from-json-path' returns a bag of doubles, 'urn:ow2:authzforce:feature:pdp:function:boolean-from-json-path' returns a bag of booleans.

This plugin is designed to be used in artifacts that generate docker images. babysaur will create a manifest file in artifacts that create docker images and you should use mamasaur in the reactor that controls them. It depends on the "modules" section and will walk down through your POM files looking for submodules of submodules. Given this does not work with Maven when building differences, you should generally NOT use multiple levels of submodules with maven reactors.

JExample is an extensions of JUnit that improves defect localizaton by changing the way you structure your tests. It introduces first-class dependencies. If test B depends on A, the return value of A can be used as B's fixture. And if A test fails, B and all other dependees of A are skipped and marked as white. We show in an empirical study that JExample improves performance and defect localization.

The clustering libraries allow you to run MMBase in a clustered environment: where multiple MMBase machines serve content from a shared database. In order to keep these machiens in sync (for instance when an object changes on one machine and the other machines needs to flush it's cache), this code must be activated. This component provides several different implementations for communication between machines, including one which depends on the 'jgroups' software.

This module groups all different output writers. Different output writers have different dependencies. To ensure that those dependencies do not leak to other output writer, or that we can limit to number of dependencies at runtime, output writers are split into separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to Graphite, there should be no need to have the AWS SDK in your classpath at runtime. Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output writers to a specific module, we can ensure this has minimal impact.

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-....