[
https://jira.codehaus.org/browse/MEAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Huss updated MEAR-166:
-----------------------------
Attachment: MEAR-166-patch.diff
A minimalist's approach
Changes:
* Modified skinny-wars test case
* Modified {{EarMojo::changeManifestClasspath()}}: Now indiscriminately does
its thing for all other modules, not just instances of {{JarModule}}.
** This means that when skinny WARs are enabled, WARs will end up on the
{{Class-Path}} manifest entry of all other modules, including other WARs.
Not what I'd call a good solution. However, as I've recently lost all interest
in the ear plugin, this is where my participation ends. Bye!
*slowly backs out of the room*
> 'skinnyWar' doesn't work well with dependencies of type 'ejb'
> -------------------------------------------------------------
>
> Key: MEAR-166
> URL: https://jira.codehaus.org/browse/MEAR-166
> Project: Maven Ear Plugin
> Issue Type: New Feature
> Affects Versions: 2.8, 2.9
> Environment: many different environments I've verified this on
> Reporter: Michal Michalski
> Priority: Minor
> Labels: contributers-welcome
> Fix For: more-investigation
>
> Attachments: MEAR-166-patch.diff
>
>
> It seems that 'skinnyWar' works OK with dependencies of type 'jar', but it
> does left 'ejb' dependencies in WEB-INF/lib. Finally, these dependencies
> exist both in EAR's lib dir and WEB-INF/lib within WAR, when using classic
> trick with both 'war'-type and 'pom'-type dependency to WAR, so all WAR's
> dependencies should go to EAR's lib.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
