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

[adrian@jboss.org]

"ALRubinger" wrote : "adrian at jboss.org" wrote : No we should use constraints (version ranges). But we need to understand how that interacts with the release process and reproducability of tagged versions.
  | 
  | Brian had this to say about current support for ranges:
  | 
  | "#maven" wrote : ALR: Brian: Don't know if you're interested, we've been running into some conflicts regarding versioning and transitive dependencies in JBossAS build.
  |   | Brian: ugh
  |   | ALR: Some use cases are documented: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131748
  |   | Brian: FWIW, i never used ranges in my corp builds
  |   | ALR: Brian: Is that a vote for "don't Mavenize"? :)
  |   | Brian: no, just don't use ranges
  | 
  | S,
  | ALR

Is that confirmation that it doesn't understand 1.0.1 > 1.0.0 like I said above.
Or is that just his preference.

There's no way we can fix dependencies at single version given the number
of projects/releases we have.

It reminds me of when I started working on the JBossAS source code using
eclipse and wondered why it was so slow.
It had never been considered that the tool should scale to such a large project. ;-)


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

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