You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Roland Asmann (JIRA)" <ji...@codehaus.org> on 2012/07/06 15:54:21 UTC
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Roland Asmann created MEAR-154:
----------------------------------
Summary: 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
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
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Posted by "Roland Asmann (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302955#comment-302955 ]
Roland Asmann edited comment on MEAR-154 at 7/7/12 3:54 AM:
------------------------------------------------------------
Also, it is not a CHOICE to package the libs into the SAR, it's the default behavior! You CAN exclude some (or all) libs -- again very similar to the WAR actually...
was (Author: asr):
Also, it is not a CHOICE to package the libs into the SAR, you can only exclude some libs -- again very similar to the WAR actually!
> 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
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Posted by "Stéphane Nicoll (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stéphane Nicoll closed MEAR-154.
--------------------------------
Resolution: Not A Bug
Assignee: Stéphane Nicoll
There's pretty much nothing the ear plugin can do at this point. Packaging dependencies in the sar is a choice that you make, you could perfectly as well not do that and rely on the transitive mechanism just for any other other library.
The duplication comes from your setup actually. If you really want to bundle these libraries in your sar, mark them as provided then.
> 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
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Posted by "Stéphane Nicoll (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stéphane Nicoll closed MEAR-154.
--------------------------------
Resolution: Won't Fix
> 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
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Posted by "Roland Asmann (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302955#comment-302955 ]
Roland Asmann commented on MEAR-154:
------------------------------------
Also, it is not a CHOICE to package the libs into the SAR, you can only exclude some libs -- again very similar to the WAR actually!
> 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
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Posted by "Stéphane Nicoll (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302960#comment-302960 ]
Stéphane Nicoll commented on MEAR-154:
--------------------------------------
except the war is considered as a final artifact by maven (no transitive dependency resolution) and the sar is just handled as a regular jar file with a special extension. These "hacks" have no relationship with the maven ear plugin. The dependency resolution mechanism is in the core. At best, your request belongs there which is why I closed this as won't fix.
> 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
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Posted by "Roland Asmann (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MEAR-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=303029#comment-303029 ]
Roland Asmann commented on MEAR-154:
------------------------------------
Why didn't you say so in the first place!?
OK, I'll think about filing this in Maven core...
> 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
[jira] (MEAR-154) SAR-Module dependencies are packaged inside the
EAR
Posted by "Roland Asmann (JIRA)" <ji...@codehaus.org>.
[ 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