Download org.opendatakit JAR files with all dependencies

Search JAR files by class name

cargo-core-tools-jboss-deployer-5 from group org.codehaus.cargo (version 1.4.19)

Remote deployer for JBoss 5.0.x

Group: org.codehaus.cargo Artifact: cargo-core-tools-jboss-deployer-5
Show documentation Show source

0 downloads

Artifact cargo-core-tools-jboss-deployer-5
Group org.codehaus.cargo
Version 1.4.19

hello-service from group org.apache.river.examples (version 1.0)

Group: org.apache.river.examples Artifact: hello-service
Show documentation Show source

0 downloads

Artifact hello-service
Group org.apache.river.examples
Version 1.0

apiconnector from group org.openml (version 1.0.10)

Ancestor for API connector libraries for specific frameworks.

Group: org.openml Artifact: apiconnector
Show documentation Show source

0 downloads

Artifact apiconnector
Group org.openml
Version 1.0.10

jr-utils from group org.zeroturnaround (version 3.0-M1)

Group: org.zeroturnaround Artifact: jr-utils
Show documentation Show source

0 downloads

Artifact jr-utils
Group org.zeroturnaround
Version 3.0-M1

redback-common-integrations from group org.apache.archiva.redback (version 2.4)

Group: org.apache.archiva.redback Artifact: redback-common-integrations
Show documentation Show source

0 downloads

Artifact redback-common-integrations
Group org.apache.archiva.redback
Version 2.4

atlas-driver-neo4j-embedded from group org.commonjava.maven.atlas (version 0.16.0)

Group: org.commonjava.maven.atlas Artifact: atlas-driver-neo4j-embedded
Show documentation Show source

0 downloads

Artifact atlas-driver-neo4j-embedded
Group org.commonjava.maven.atlas
Version 0.16.0

ng2-material from group org.webjars.npm (version 0.4.1)

WebJar for ng2-material

Group: org.webjars.npm Artifact: ng2-material
Show documentation Show source

0 downloads

Artifact ng2-material
Group org.webjars.npm
Version 0.4.1

taverna-reference-testhelpers from group org.apache.taverna.engine (version 3.1.0-incubating)

In order to properly test OSGi-loaded t2ference modules we need a module that is entire external to t2reference and to the test cases. If the test implementations are included in either the api, core implementations or test modules they will be loaded by the root classloader of the test runner - by putting them in an independent artifact we allow them to be loaded through various SPI discovery mechanisms as they would be in a 'real' environment.