"wolfc" wrote : The aim of the game is not to get an unified assembly, but to
get a diverse set of components which can form different assemblies. For example EJB 3 +
Remoting 3, EJB 3 + QOS Cache, or just EJB 3 lite. Thus satisfying more use cases with
less code bases.
I agree.
Then jboss-ejb3 should not declare dependencies, but rather configure the versions to be
used for dependencyManagement.
So jboss-ejb3 becomes a POM project decending from jboss-ejb3-build, and as5-int, as6-int,
ejb3-embeddable, ejb3-plugin use jboss-ejb3 as a parent. The unified assemblies can come
the final projects in the chain.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206622#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...