"project" is also a pretty bad name, I don't have a knack for this. Suggestions for one word that signify that "this module has all transitive dependencies and defines an EJB3 release" are appreciated.

assembly?
composite?
ejb3? (like: org.jboss.ejb3:ejb3)

S,
ALR

Some more thoughts:

Naming

I like "org.jboss.ejb3:jboss-ejb3"

Remove the component artifacts from JBossAS

If we provide a unified assembly for all EJB3 projects, then we may provide "jboss-ejb3.jar" as one artifact into AS. This provides the following benefits:

1) No more user confusion as to what version of the EJB3 project is in AS. A check into the manifest will simply say "1.0.0".

2) Removes the half-upgraded problem. Users won't be upgrading ejb3-core while neglecting to update ejb3-proxy or ejb3-common.

3) We can do away with the explicit dependencies upon the client classifier JARs:

<version.org.jboss.ejb3>1.0.0</version.org.jboss.ejb3> < This one stays
 <version.org.jboss.ejb3.common.client>1.0.0</version.org.jboss.ejb3.common.client>
 <version.org.jboss.ejb3.core.client>1.0.0</version.org.jboss.ejb3.core.client>
 <version.org.jboss.ejb3.proxy.client>1.0.0</version.org.jboss.ejb3.proxy.client>
 <version.org.jboss.ejb3.proxy.clustered.client>1.0.0</version.org.jboss.ejb3.proxy.clustered.client>
 <version.org.jboss.ejb3.security.client>1.0.0</version.org.jboss.ejb3.security.client>

"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.