You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marcel Schutte (JIRA)" <ji...@codehaus.org> on 2006/12/31 18:32:09 UTC
[jira] Created: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
ejb-client dependencies should not be treated as J2EE application client modules
--------------------------------------------------------------------------------
Key: MEAR-53
URL: http://jira.codehaus.org/browse/MEAR-53
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: mvn 2.0.4
Reporter: Marcel Schutte
With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MEAR-53) ejb-client dependencies should not
be treated as J2EE application client modules
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=all ]
Work on MEAR-53 started by Stephane Nicoll.
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
> Assigned To: Stephane Nicoll
> Fix For: 2.3.1
>
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=all ]
Stephane Nicoll closed MEAR-53.
-------------------------------
Resolution: Fixed
This is fixed, a SNAPSHOT has been deployed on the apache repository
http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-ear-plugin/2.3.1-SNAPSHOT/
Could you please test with this version. If you're happy with it, we'll make sure to release it ASAP.
Thanks for the report.
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
> Assigned To: Stephane Nicoll
> Fix For: 2.3.1
>
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
Posted by "Stephen Coy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=comments#action_83697 ]
Stephen Coy commented on MEAR-53:
---------------------------------
I agree that adding ejb-client type artifacts as modules by default is incorrect. In fact, it should be completely unnecessary to have these kinds of artiifacts in an ear file, unless they refer to ejbs in a different ear. Application server classloaders make the ejb interfaces visible to other modules by default within an ear file.
Default behaviour should always be spec conformant.
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
Posted by "Marcel Schutte (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104746 ]
Marcel Schutte commented on MEAR-53:
------------------------------------
Stephane,
Could you please release 2.3.1. This issue was fixed 7 months ago and I need this fix very urgently now.
Thx, Marcel
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
> Assignee: Stephane Nicoll
> Fix For: 2.3.1
>
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
Posted by "Marcel Schutte (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=comments#action_84036 ]
Marcel Schutte commented on MEAR-53:
------------------------------------
I've done a test with version 2.3.1-SNAPSHOT and it works as expected.
Thanks for your quick reaction.
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
> Assigned To: Stephane Nicoll
> Fix For: 2.3.1
>
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104766 ]
Stephane Nicoll commented on MEAR-53:
-------------------------------------
Hi Marcel,
Thanks for the reminder. I just called a vote on the dev list. If all goes well, it will be available this week.
Cheers,
Stpéhane
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
> Assignee: Stephane Nicoll
> Fix For: 2.3.1
>
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=comments#action_83711 ]
Stephane Nicoll commented on MEAR-53:
-------------------------------------
the spec has not always been very clear on that point I am afraid.
I don't know of any concrete use case of application-client. I don't think that we even have a artifact type for this kind of project. So the real question here is when the <java> entry is actually used in a deployment descriptor.
I agree this is a bug.
{quote}
I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
{quote}
It has nothing to do with that, it's a misunderstanding of the usage of the <java> module element. If you work with regular jar artifact type, they are not included in the application.xml unless specified explicitely, only ejb-clients are for the moment.
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEAR-53) ejb-client dependencies should not be
treated as J2EE application client modules
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-53?page=all ]
Stephane Nicoll updated MEAR-53:
--------------------------------
Fix Version/s: 2.3.1
> ejb-client dependencies should not be treated as J2EE application client modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: http://jira.codehaus.org/browse/MEAR-53
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
> Assigned To: Stephane Nicoll
> Fix For: 2.3.1
>
>
> With the release of maven-ear-plugin 2.3, it has become default behavior to include a <module><java> tag in the generated application.xml for dependencies of type ejb-client.
> This is not the intended use of the <module><java> tag and it also causes errors in Websphere 5.1. <module><java> is for application client modules (j2ee modules with an application-client.xml deployment descriptor) and certainly not for ejb-client jars (which are from a j2ee perspective regular java jar files).
> I understand from the discussion in MEAR-46 that JBoss users sometimes use the <module><java> tags as a means to document the jars that make up an ear. This is al fine, but don't make this the default.
> I suggest turning the behavior around and switching the default to no inclusion in the generated application.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira