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

[Paul Gier (JIRA)]

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

Paul Gier commented on JBBUILD-534:
-----------------------------------

There was some discussion on the maven developers list about repository synching, and how we can manage synchronization with our dependencies on rebuilt stuff (for example all the jars with "-brew" at the end).  We can't send them to the central repository because they are not our upstream projects, but we need them for building projects like the app server.  So it doesn't really do us any good to synchronize the jboss app server jars to central if we can't also send the dependencies.  So the recommendation is to change the groupId of our rebuilt artifacts and prefix it with something like "org.jboss".  If we use a groupId like this then we could avoid conflicts caused by rebuilt artifacts.  But this would cause other problems [1].

[1]http://www.nabble.com/Depending-on-Artifacts-not-in-central-td24394458.html

> 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