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

[ALRubinger]

"dimitris at jboss.org" wrote : Having the AS pom.xml essentially outside the project.

That's much different than "the component-matrix pom is a bad idea". :)

----

Though I don't much care where component-matrix lives, we've got conflicting views on the topic of what constitutes a circular dependency.

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

I don't agree with the above statement.  The Thread at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132229 explains this more fully.  In short, the dependency chain can be "AS Assembly > EJB3 > AS Component" just fine.

However, if Adrian's comment is true, then moving the component-matrix POM under jbossas/trunk means we cannot depend on it, which defeats its purpose in the first place.

----

"dimitris at jboss.org" wrote : 1) Your mission is to deliver a working EJB3 implementation, not screw up the AS build.

We've outgrown the current layout of JBossAS.  EJB3, webservices, (messaging?), and any future projects need to take advantage of the same libraries/projects that AS does.  JBossAS cannot lay claim to exclusive control of these projects.

We need to discuss and come to agreement on the direction in which we're heading by identifying the requisite use cases for both AS and AS Component Consumers.

Let's try to give that some attention this week.

S,
ALR


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

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