You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org> on 2014/06/15 15:03:10 UTC

[jira] (MEAR-153) Skinny Modules -- not just WARs

     [ https://jira.codehaus.org/browse/MEAR-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl-Heinz Marbaise updated MEAR-153:
-------------------------------------

    Fix Version/s: more-investigation

> Skinny Modules -- not just WARs
> -------------------------------
>
>                 Key: MEAR-153
>                 URL: https://jira.codehaus.org/browse/MEAR-153
>             Project: Maven Ear Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.7
>            Reporter: Roland Asmann
>             Fix For: more-investigation
>
>         Attachments: AbstractEarModule.java.patch, SarModule.java.patch
>
>
> Currently it is only possible to have the plugin filter WARs to get them 'skinny', however this could be very useful for other modules as well!
> In my project I have both a WAR and a SAR that should share several libraries. As standalone artifacts, they should both package it themselves, but in the deployed EAR I get classloading-errors when they don't have the libs shared in the EAR.
> I traced a solution to the method 'EarModule.getLibDir()', which is only implemented with a value in the 'WebModule'-subclass.
> Since I am not familiar with all the module-types, I attached a solution that ONLY handles the SarModule, but this can probably used in all other Modules that contain libs as well.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)