[jboss-dev-forums] [Design of JBoss Build System] - Re: Shared Parent POM for dependencyManagement

[adrian@jboss.org]

"wolfc" wrote : then we must at least get an exception if there is a version conflict. It is already happening that the wrong version is showing up at the end.
  | I'm not going to babysit poms.

My question still stands (for Dimitris as well), 
how do you know what the correct version is?

e.g. suppose jbossas upgraded ejb3 to 3.0.1 which requires xyz:1.0.1
some other project uses xyz:1.0.0

JBossAS updates its pom to xyz:1.0.1 thereby saying the issue/conflict is resolved

Later ejb3:3.0.2 says xyz:1.0.2 is required,
how does it know that the xyz:1.0.1 in the jbossas pom isn't already resolving the conflict?

Sure you could add a constraint


  | xyz:[1.0.2,)
  | 

But then how do you reproduce your build?
i.e. you need to choose a specific version in your pom.xml that gets tagged in svn,
but still have the open constraint in the one that goes in the repository.

Has anybody tried this, does it work?
Does it play nicely with snapshots? :-)

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

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