[
https://issues.apache.org/jira/browse/MEAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958942#comment-17958942
]
Matthias Bünger commented on MEAR-53:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ear-plugin#240|https://github.com/apache/maven-ear-plugin/issues/240].
> ejb-client dependencies should not be treated as J2EE application client
> modules
> --------------------------------------------------------------------------------
>
> Key: MEAR-53
> URL: https://issues.apache.org/jira/browse/MEAR-53
> Project: Maven EAR Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: mvn 2.0.4
> Reporter: Marcel Schutte
> Assignee: Stephane Nicoll
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
