[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project

Tue Apr 22 18:36:44 EDT 2008

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=comments#action_12410140 ] 

Anil Saldhana commented on EJBTHREE-1315:
-----------------------------------------

Yes, I did that too.  Naming the id to client would give us the jar name we want. There was an issue with ejb3/plugin/src..../installer.xml or somewhere else where u need to specify the id of the all the client jars for assembly.  finalName was useless too.

As I said, we need more options on the assembly plugin to get a final mapped name that is exactly the one specified in the options.

> 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