[
http://jira.codehaus.org/browse/MEAR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100015
]
Stefan Seidel commented on MEAR-69:
-----------------------------------
Of course it is somewhere in the dependencies - transitively. It is just common
practice: typically, an EAR consists of EJBs and WARs. The WARs have
dependencies on the EJB as ejb-client (because they only need to access the
interfaces), and thus there are transitive dependencies of type ejb-client in
the EAR project.
Can you give me one example where ejb and ejb-client need to be included in the
same EAR? In fact, this will most likely violate class loading constraints,
because the same class files are present twice.
I know that I can exclude them with module tags, but this seems much more of a
workaround.
> Both ejb-client and ejb JARs of the same artifact are included
> --------------------------------------------------------------
>
> Key: MEAR-69
> URL: http://jira.codehaus.org/browse/MEAR-69
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.3, 2.3.1
> Reporter: Stefan Seidel
> Assignee: Stephane Nicoll
> Priority: Minor
>
> When the dependencies of the EAR include both the <type>ejb</type> and
> <type>ejb-client</type> dependencies of the same artifact, both JAR files are
> included in the EAR - which really doesn't make much sense to me, as all
> files of the client-jar should be included in the ejb-jar as well.
--
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
