[jboss-dev-forums] [Design of JBoss Build System] - Re: Move dependency management back into app server svn stru

[adrian@jboss.org]

"wolfc" wrote : I've got a nice analogy now: go back to Paul's original post and substitute 'component-matrix' with 'Hibernate' or 'jboss-logging' or any other common component.
  | 
  | The arguments presented by Paul will still hold up, yet we do not want these things in the AS trunk.

That's a logical fallacy, in fact probably a few of them. :-)

I only have to do the exercise proposed to see its not true.

anonymous wrote : 
  | After spending some time updating dependencies in the HIBERNATE pom while working on the build-thirdparty conversion, it seems that having ... HIBERNATE as a separate project is somewhat error prone.
  | 
  | The main issue is that whenever I make a change in ... HIBERNATE I have to make sure that the app server is immediately updated to match, otherwise there are build errors.
  | 

Which plainly isn't true.

There's a big difference between an external project that is included in JBossAS 
as a component and an external project that actually defines what 
those components should be.

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

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