Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: Repository Support 2010
Component/s: Maven Builds
Similar Issues:Show 10 results
JBBUILD-689 Add JGit repository to Maven repository JBBUILD-597 Synchronize JBoss artifacts from the JBoss repository to the Maven central repository JBBUILD-344 Add ability to deploy aggregage projects (ejb3 api) to the jboss repository. JBBUILD-293 Update dependencies in maven repository JBBUILD-340 Create maven plugin to deploy artifacts to the non-maven jboss repository. JBBUILD-686 Download statistics for the maven repository JBBUILD-584 Add junit 4.8.1 to maven repository JBBUILD-647 Add maven-cli-plugin repository to proxy repositories JBBUILD-449 Add metamatrix users to maven repository committers. JBBUILD-176 Look into populating the public maven repository with jboss release binaries
There are a number of projects which have dependencies on non-jboss
maven repos (jboss-osgi is one of them)
I believe, this issue is general enough to have proper repo aggregation
Here is a link to some aggregators
Is this a way you want to move forward or should we stick with manually copying individual artefacts to the jboss repo?
Please note, that by doing so (i.e. mvn deploy-file) you loose the original pom and hence the information on transitive dependencies.