Download JAR files tagged by conflicts with all dependencies
metrics-bom from group com.covisint.core (version 3.0.2)
This bill of materials (BOM) POM covers all the Metrics artifacts related to a particular version.
By importing this BOM, you fix the version of all of Metrics-related artifacts to the versions
associated with a particular release. This prevents the overriding of Metrics 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>metrics-bom</artifactId>
<version>3.0.2</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
And then declare your dependency on the Metrics artifacts *without* a version.
Group: com.covisint.core Artifact: metrics-bom
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact metrics-bom
Group com.covisint.core
Version 3.0.2
Last update 22. April 2015
Organization not specified
URL http://covisint.com
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.covisint.core
Version 3.0.2
Last update 22. April 2015
Organization not specified
URL http://covisint.com
License The Apache Software License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
listenablefuture from group com.google.guava (version 9999.0-empty-to-avoid-conflict-with-guava)
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-....
Artifact listenablefuture
Group com.google.guava
Version 9999.0-empty-to-avoid-conflict-with-guava
Last update 11. September 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.google.guava
Version 9999.0-empty-to-avoid-conflict-with-guava
Last update 11. September 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
data-distribution-api-vivo_1_09 from group edu.cornell.library.scholars (version 1.1.1)
---------------------------------------------------------------------------
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.
---------------------------------------------------------------------------
Group: edu.cornell.library.scholars Artifact: data-distribution-api-vivo_1_09
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact data-distribution-api-vivo_1_09
Group edu.cornell.library.scholars
Version 1.1.1
Last update 25. April 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies vitro-api, vitro-dependencies,
There are maybe transitive dependencies!
Group edu.cornell.library.scholars
Version 1.1.1
Last update 25. April 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies vitro-api, vitro-dependencies,
There are maybe transitive dependencies!
deployment-client from group de.schlichtherle.glassfish (version 4.0)
This is an endorsed version of the original Deployment Client for
Oracle GlassFish Open Source Edition.
The purpose of the endorsement is to provide a shaded JAR which has the
OSGI meta data removed because it causes the original Deployment Client
to fail when used within a module running within a GlassFish container
due to some class loader configuration conflicts between the container
and the deployed module.
This issue has been reported to the GlassFish project at
https://java.net/jira/browse/GLASSFISH-20856 .
It is hoped that it can get fixed so that this workaround project can
get deprecated soon.
0 downloads
Artifact deployment-client
Group de.schlichtherle.glassfish
Version 4.0
Last update 21. October 2013
Organization not specified
URL https://bitbucket.org/christian_schlichtherle/glassfish-deployment-client
License CDDL + GPLv2 with classpath exception
Dependencies amount 50
Dependencies common-util, core, hk2-locator, javax.inject, cglib, hk2-utils, glassfish-api, scattered-archive-api, nucleus-grizzly-all, grizzly-framework, grizzly-rcm, grizzly-portunif, grizzly-http, grizzly-http-server, grizzly-config, admin-cli, hk2, hk2-api, osgi-resource-locator, config-types, hk2-config, tiger-types, bean-validator, hk2-runlevel, class-model, mimepull, jettison, stax-api, launcher, logging, admin-util, config-api, security-services, security, ssl-impl, ldapbp-repackaged, jackson-core-asl, simple-glassfish-api, javax.enterprise.deploy-api, deployment-common, internal-api, management-api, gmbal, pfl-basic, pfl-tf, pfl-asm, pfl-dynamic, pfl-basic-tools, pfl-tf-tools, asm-all-repackaged,
There are maybe transitive dependencies!
Group de.schlichtherle.glassfish
Version 4.0
Last update 21. October 2013
Organization not specified
URL https://bitbucket.org/christian_schlichtherle/glassfish-deployment-client
License CDDL + GPLv2 with classpath exception
Dependencies amount 50
Dependencies common-util, core, hk2-locator, javax.inject, cglib, hk2-utils, glassfish-api, scattered-archive-api, nucleus-grizzly-all, grizzly-framework, grizzly-rcm, grizzly-portunif, grizzly-http, grizzly-http-server, grizzly-config, admin-cli, hk2, hk2-api, osgi-resource-locator, config-types, hk2-config, tiger-types, bean-validator, hk2-runlevel, class-model, mimepull, jettison, stax-api, launcher, logging, admin-util, config-api, security-services, security, ssl-impl, ldapbp-repackaged, jackson-core-asl, simple-glassfish-api, javax.enterprise.deploy-api, deployment-common, internal-api, management-api, gmbal, pfl-basic, pfl-tf, pfl-asm, pfl-dynamic, pfl-basic-tools, pfl-tf-tools, asm-all-repackaged,
There are maybe transitive dependencies!
third-party from group uk.org.retep.third-party (version 10.1)
This repository contains various third party sources required by the main
retepTools repository.
The reason for this is when they are only available in SNAPSHOT format and
we require a release version to enable us to run a release.
Although not ideal, this is sometimes necessary if some critical bug needs to
be fixed.
Currently this contains docbkx-tools.
Rules for this repository:
* Projects must follow the same licensing as the main project :-
BSD, Apache2 etc but not GPL, LGPL etc
* groupId's must be within the uk.org.retep.third-party namespace - and not
the projects original namespace (so we don't have version conflicts)
* Must be disabled/removed once those projects become stable
Group: uk.org.retep.third-party Artifact: third-party
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact third-party
Group uk.org.retep.third-party
Version 10.1
Last update 29. January 2010
Organization Retep Development Group
URL http://kenai.com/projects/reteptools
License BSD
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group uk.org.retep.third-party
Version 10.1
Last update 29. January 2010
Organization Retep Development Group
URL http://kenai.com/projects/reteptools
License BSD
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
data-distribution-api-vivo_1_08 from group edu.cornell.library.scholars (version 1.1.1)
---------------------------------------------------------------------------
Version for VIVO 1.8
This uses the source and test code from the Version for VIVO 1.10, edited to
make it compatible with VIVO 1.8. It also borrows some code from VIVO 1.10
itself, changes the package name to avoid conflicts, and adds it here.
* Vitro 1.8 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.8 does not have a "...webapp.utils.sparqlrunner" package, so
borrow the source from Vitro 1.10, move it to a different package (just
for compatibility 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.
---------------------------------------------------------------------------
Because VIVO 1.8 is not available as a Maven package, we have extracted the
class files, JARed them up, and stored them in a file-based repository
within this project.
But that doesn't include any transitive dependencies, so any package that
this code requires must be explicitly listed as a dependency.
---------------------------------------------------------------------------
Group: edu.cornell.library.scholars Artifact: data-distribution-api-vivo_1_08
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact data-distribution-api-vivo_1_08
Group edu.cornell.library.scholars
Version 1.1.1
Last update 25. April 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 9
Dependencies vivo_classes, jena-core, jena-arq, commons-logging, commons-io, commons-lang, jackson-core, jackson-databind, jackson-annotations,
There are maybe transitive dependencies!
Group edu.cornell.library.scholars
Version 1.1.1
Last update 25. April 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 9
Dependencies vivo_classes, jena-core, jena-arq, commons-logging, commons-io, commons-lang, jackson-core, jackson-databind, jackson-annotations,
There are maybe transitive dependencies!
Page 5 from 5 (items total 46)