EJB3 Artifact Assemblies

[alrubinger]

Under jbossas/trunk/ejb3/src/assembly are a series of Maven2 Assembly Configurations:

jboss-ejb3.xml
jboss-ejb3-client.xml
hibernate-client.xml

Looks like "jboss-ejb3-client" is duplicated from the config of same name located in EJB3 Core. EJB3 Core has no notion of "hibernate-client", and I imagine jboss-ejb3 is there to contain most org.jboss.ejb3 classes.

How do we want to handle unifying these with projects/trunk/ejb3? At the very least, jboss-ejb3-client is a duplicate; perhaps the other two are AS-specific?

First thought that comes to mind is a new artifact under EJB3, "assembly" to contain these. Then the dependency plugin can bring these in, unpack under "target", and let them be used by the assembly plugin to create custom artifacts.

S,
ALR

[alrubinger]

EJB3 Core Client is also available in 3rdparty as:

thirdparty/jboss/jboss-ejb3-core/lib/jboss-ejb3-core-client.jar

S,
ALR

[wolfc]

The whole of AS trunk/ejb3 should disappear. It contains code which either has another function than ejb3 (e.g. appclient), deployers which need separating out or dead code.

Hibernate-client needs to move to Hibernate team, it's silly to have that in EJB3 or AS.

Anyway these assemblies do not affect projects/ejb3.