[Jboss-dev-forums] [Design of JBoss Build System] - Re: Requirements - Top level build - versioning

[<rya...@jb...>]

"ad...@jb..." wrote : 
  | 1) Who is reponsible for the versions used
  | a) the top level buld
  | b) the component
  | c) something else
  | 

The solution we've discussed elsewhere is that a graph of dependencies should be built based on the union of dependencies from each component.  So:

1.  Components define their version compatibilities
2.  The toplevel build chooses the version acceptable to all components?
3.  It also seems we have a requirement for the toplevel build to "peg" a component at a given version.  For instance log4j as above, and of course any directly referenced components such as jms.


anonymous wrote : 
  | 2) How are conflicts resolved
  | a) by changing the top level build
  | b) by changing the offending component
  | c) other
  | 

There are 2 kinds of conflicts:

1.  Conflicts which occur during synchronization.  That is, that two components can not agree on a depedency's version -- preventing synchronization from completing (Or would a conflict not prevent synchronization?).

In this case, you could either resolve it by modifying one of the components to be more agreeable (ie, test it with the new version).  Or you could "peg" the toplevel build to a given version of that dependency, which would remove the ambiguity?

2.  Conflicts that occur during materialization.  This would produce warnings if a component is incompatible with a pegged version of another component, as a result of #1.



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

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