1:48 p.m.
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
4:23 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=comments#action_1241... ]
Carlo de Wolf commented on EJBTHREE-1315:
-----------------------------------------
If I change the id in jboss-ejb3-client.xml to 'client' then I get the right
artifact name.
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
5:10 p.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=all ]
Andrew Lee Rubinger resolved EJBTHREE-1315.
-------------------------------------------
Resolution: Rejected
Each EJB3 Project will be responsible for making its own client Assembly.
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
5:13 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=comments#action_1241... ]
Andrew Lee Rubinger commented on EJBTHREE-1315:
-----------------------------------------------
Carlo: "If I change the id in jboss-ejb3-client.xml to 'client' then I get
the right artifact name."
The error becomes present when "attach" is set to true, and this is required.
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
5:25 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=comments#action_1241... ]
Anil Saldhana commented on EJBTHREE-1315:
-----------------------------------------
I did exactly the steps you are mentioning before I dumped the idea of creating a separate
client.xml for security.
The artifact names seemed crazy (we need more options on the assembly plugin) to get this
right.
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
5:28 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=comments#action_1241... ]
Andrew Lee Rubinger commented on EJBTHREE-1315:
-----------------------------------------------
"The error becomes present when "attach" is set to true, and this is
required."
Correction, when both "attach" is true and "finalName" is specified.
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
5:30 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=comments#action_1241... ]
Andrew Lee Rubinger commented on EJBTHREE-1315:
-----------------------------------------------
"The artifact names seemed crazy (we need more options on the assembly plugin) to get
this right."
If you specify ID of "client", Anil, the JAR name would be
"jboss-ejb3-security-client.jar".
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
5:34 p.m.
New subject: [JBoss JIRA] Reopened: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=all ]
Andrew Lee Rubinger reopened EJBTHREE-1315:
-------------------------------------------
Reopening to discuss on Forum the validity of this issue.
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
5:36 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=comments#action_1241... ]
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
6:03 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ http://jira.jboss.com/jira/browse/EJBTHREE-1315?page=all ]
Andrew Lee Rubinger updated EJBTHREE-1315:
------------------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145998
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
8:23 p.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-1315) Make EJB3 Client Assembly its own Project
[ 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
6661
days inactive
6663
days old
10 comments
3 participants
participants (3)
-
Andrew Lee Rubinger (JIRA) -
Anil Saldhana (JIRA)
-
Carlo de Wolf (JIRA)