[jira] [Commented] (MEAR-166) 'skinnyWar' doesn't work well with dependencies of type 'ejb'

["Anders Hammar (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MEAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008972#comment-17008972 ] 

Anders Hammar commented on MEAR-166:
------------------------------------

This use case does make sense to me and I was just hit by it.

My scenario is a war which has a dependency to an ejb3 (jpa) artifact which it has a declared (runtime) dependency to. But I'd like the ejb to be on ear level as several other artifacts has this dependency. The idea with the skinnyWar feature, IMHO, is to have all war projects correctly specifying their dependencies (as it would be deployed alone) and then have the ear massaging them to be skinny when included in an ear. This should include ejb artifacts as well as jar libraries.

> 'skinnyWar' doesn't work well with dependencies of type 'ejb'
> -------------------------------------------------------------
>
>                 Key: MEAR-166
>                 URL: https://issues.apache.org/jira/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: EAR without EJB dependencies.patch, MEAR-166-patch.diff
>
>
> It seems that 'skinnyWar' works OK with dependencies of type 'jar', but it does leave '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
(v8.3.4#803005)