[
http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=all ]
Andrew Lee Rubinger resolved EJBTHREE-1315.
-------------------------------------------
Resolution: Rejected
For the time being, we'll follow Carlo's road and give each module its own client
assembly, to be brought in as dependencies of "plugin".
Make EJB3 Client Assembly its own Project
-----------------------------------------
Key: EJBTHREE-1315
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-1315
Project: EJB 3.0
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: AS 5.0.0.CR1
The EJB3 Client JAR should be assembled by its own project because:
* It may incorporate classes from any of the EJB3 Projects, not just Core
* Renaming to finalName "jboss-ejb3-client" is not possible from within Core as
the artifact must both be attached to the build and the "finalName" property
does not change the artifactId (as we're currently using a classifier). This leads
to:
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{org.jboss.ejb3:jboss-ejb3-core:0.1.0-SNAPSHOT:jar}: An attached artifact must have a
different ID than its corresponding main artifact.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira