Hi Folks,
I absolutely agree this should not be a human task.
Richard
Thomas Diesler wrote:
Folks,
there are a number of projects which have dependencies on non jboss
maven repos (jboss-osgi is one of them)
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235779#...
I believe, this issue is general enough to have proper repo
aggregation setup somehow
Here is a link to some aggregators
http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Featu...
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.
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
In the jboss repo, there are many artefacts with a generated
(meaningless) pom already.
cheers
-thomas
--
Richard Opalka
JBoss Software Engineer
Mail: ropalka(a)redhat.com
Mobile: +420 731 186 942