You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marat Abrarov (Jira)" <ji...@apache.org> on 2020/10/12 18:12:00 UTC
[jira] [Commented] (MEAR-166) 'skinnyWar' doesn't work well with
dependencies of type 'ejb'
[ https://issues.apache.org/jira/browse/MEAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212564#comment-17212564 ]
Marat Abrarov commented on MEAR-166:
------------------------------------
[~afloom], could you please provide a minimal maven project to reproduce your use case?
> '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)