[
https://jira.codehaus.org/browse/MEAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348048#comment-348048
]
Karl-Heinz Marbaise edited comment on MEAR-166 at 6/15/14 8:00 AM:
-------------------------------------------------------------------
Created an [example
project|https://github.com/khmarbaise/mear/tree/master/MEAR-166] which shows
the wrong behaviour:
{code}
ear-module/target/ear-module-1.0
|-- META-INF
| `-- application.xml
|-- ejb-module-1.0.jar
|-- lib
| `-- commons-lang-2.5.jar
`-- war-module-1.0.war
{code}
unfortunately the war file contains the ejb jar file:
{code}
Archive: ear-module/target/ear-module-1.0/war-module-1.0.war
testing: META-INF/ OK
testing: META-INF/maven/ OK
testing: META-INF/maven/org.apache.maven.its.ear.skinnywars/ OK
testing: META-INF/maven/org.apache.maven.its.ear.skinnywars/war-module/ OK
testing: WEB-INF/ OK
testing: WEB-INF/classes/ OK
testing: WEB-INF/lib/ OK
testing: META-INF/INDEX.LIST OK
testing: META-INF/MANIFEST.MF OK
testing:
META-INF/maven/org.apache.maven.its.ear.skinnywars/war-module/pom.properties
OK
testing:
META-INF/maven/org.apache.maven.its.ear.skinnywars/war-module/pom.xml OK
**testing: WEB-INF/lib/ejb-module-1.0.jar OK**
testing: WEB-INF/web.xml OK
{code}
So taking a deeper look into the code it is not supported at the moment. The
questions is: Does this make sense? Defining the dep on ejb within the war
module which itself will be put into EAR ? (I'm not sure about that kind of use
case. Has someone a good example for this? In my opinion using a ejb-client as
a dep in the war module would make more sense to me.
was (Author: khmarbaise):
Created an [example
project|https://github.com/khmarbaise/mear/tree/master/MEAR-166] which shows
the wrong behaviour:
{code}
ear-module/target/ear-module-1.0
|-- META-INF
| `-- application.xml
|-- ejb-module-1.0.jar
|-- lib
| `-- commons-lang-2.5.jar
`-- war-module-1.0.war
{code}
unfortunately the war file contains the ejb jar file:
{code}
Archive: ear-module/target/ear-module-1.0/war-module-1.0.war
testing: META-INF/ OK
testing: META-INF/maven/ OK
testing: META-INF/maven/org.apache.maven.its.ear.skinnywars/ OK
testing: META-INF/maven/org.apache.maven.its.ear.skinnywars/war-module/ OK
testing: WEB-INF/ OK
testing: WEB-INF/classes/ OK
testing: WEB-INF/lib/ OK
testing: META-INF/INDEX.LIST OK
testing: META-INF/MANIFEST.MF OK
testing:
META-INF/maven/org.apache.maven.its.ear.skinnywars/war-module/pom.properties
OK
testing:
META-INF/maven/org.apache.maven.its.ear.skinnywars/war-module/pom.xml OK
**testing: WEB-INF/lib/ejb-module-1.0.jar OK**
testing: WEB-INF/web.xml OK
{code}
So taking a deeper look into the code it is not supported at the moment. The
questions is: Does this make sense? Defining the dep on ejb within the war
module which itself will be put into EAR ? (I'm not sure about that kind of use
case. Has someone a good example for this?
> '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
> Fix For: more-investigation
>
>
> 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)
