[jboss-dev-forums] [Design of JBoss Build System] - Re: AS Components Bound to AS Release Cycle

[ALRubinger]

"adrian at jboss.org" wrote : If you depend upon a jbossas sub-project then you are doing it wrong.  Circular dependency anyone? :-)

This is the pattern we'd laid out.  We avoid circular dependency by:

( -> == "Depends on")

* EJB3 -> AS Components
* AS -> AS Components, EJB3

...where AS itself is just an Assembly of modules.  No AS Components may depend on any AS Component Consumer (ie. EJB3).

"adrian at jboss.org" wrote : Your dependency should be on the integration-spi (which should not change) not implementation details. 

Yes, I'd like to see more use of the integration project for well-defined SPIs between modules/projects, but for now it's one step at a time.  Else we'll never release anything.

The goal is to keep untangling interdependent modules; I'd like to see the day when we have enough separation that the monolithic structure of AS can disintegrate.

"adrian at jboss.org" wrote : But then again, the aspects project is an abortion anyway I've been complaining about it for years :-( 

Was just an example, but you get the point. :)

S,
ALR

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

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