[
https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Asmann reopened MEAR-154:
--------------------------------
How is this in my setup?
In the SAR I have a normal list of dependencies, which imho SHOULD be packaged
inside the SAR. Then in the EAR I only have a dependency on the SAR.
Why is this handled differently compared to eg a WAR artifact? I have the exact
same dependency-setup in the SAR and WAR, but only when packaging the SAR into
an EAR, the transitive dependencies get collected.
If you are so sure it is a setup-thing, then explain to me why it doesn't do
this with the WAR as well?
> SAR-Module dependencies are packaged inside the EAR
> ---------------------------------------------------
>
> Key: MEAR-154
> URL: https://jira.codehaus.org/browse/MEAR-154
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Reporter: Roland Asmann
> Assignee: Stéphane Nicoll
>
> When I package a SAR-Module into my EAR, all depencies to the SAR are
> resolved and added to the EAR. The problem here is that these dependencies
> are already packaged inside the SAR, making for a very large EAR and
> sometimes classloading-problems!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
