[
https://issues.apache.org/jira/browse/MEAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marat Abrarov updated MEAR-166:
-------------------------------
Comment: was deleted
(was: [~afloom], could you please provide a minimal maven project to reproduce
your use case? It looks like you don't follow
[https://maven.apache.org/plugins/maven-ear-plugin/examples/skinny-wars.html]
(refer to "the painful part"). I use [this
trick|https://github.com/mabrarov/maven-ear-plugin/blob/ea215eef8ea4cf429a793c29a15b6d48b7fe095c/src/test/resources/projects/project-092/ear/pom.xml#L40]
with {{<type>pom</type>}} to include all dependencies of EAR modules (of
{{eartest:war-sample-two:war}}) into EAR.)
> '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)
