[jboss-dev-forums] [Design of JBoss Build System] - Re: Dependency conflicts lost during AS mavenization

[pgier]

"heiko.braun at jboss.com" wrote : I'd like to remove all legacy artifacts (wrong group-id) from the repo. This would force anyone to update (because the build breaks). But I am not sure about the implications. 
  | 
  | Does this require any dependent project to republish it's artifacts and pom or can an existing repo artifacts simply be updated?

The risk of doing this is that it can break old builds that depend on the old groupId.  The official maven way to move artifacts around in a repository is to add a relocation configuration to the pom (http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_relocation).

What would you think if we create a new location in the repository for stuff that is in the repository but should have been in a different place?

So maybe something like http://repository.jboss.org/maven2_legacy.
This way we can remove stuff from the main repository to make it cleaner, and if we want to build older releases that depend on some of these things, this legacy repo location just needs to be added to settings.xml.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140978#4140978

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140978