[
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
