[jboss-jira] [JBoss JIRA] Commented: (JBBUILD-534) Maven repository aggregation

[Thomas Diesler (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBBUILD-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12476318#action_12476318 ] 

Thomas Diesler commented on JBBUILD-534:
----------------------------------------

Please also note, that even if you preserve the original POM on 'deploy-file' it is likely that the deployed file itself has dependencies on artefacts in other repositories.

> Maven repository aggregation
> ----------------------------
>
>                 Key: JBBUILD-534
>                 URL: https://jira.jboss.org/jira/browse/JBBUILD-534
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven Builds
>            Reporter: Thomas Diesler
>
> 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#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+Feature+Matrix
> 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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira