[ https://issues.apache.org/jira/browse/MEAR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213119#comment-17213119 ]
Hudson commented on MEAR-267: ----------------------------- Build succeeded in Jenkins: Maven » Maven TLP » maven-ear-plugin » 19 #4 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-ear-plugin/job/19/4/ > assembly.xml contains incorrect references to modules > ----------------------------------------------------- > > Key: MEAR-267 > URL: https://issues.apache.org/jira/browse/MEAR-267 > Project: Maven Ear Plugin > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: Leonid Rozenblyum > Priority: Major > > SCENARIO: > Create a EAR project with maven-ear-plugin 3.0.0 > execute mvn ear:ear > EXPECTED: > assembly.xml contains reference to the jar/war equivalent to their physical > names inside > the EAR > (e.g. if the jar is named tryEar-ejb-1.0-SNAPSHOT.jar then assembly.xml > reference would be: > {quote}{{<module>}} > <ejb>tryEar-ejb-1.0-SNAPSHOT.jar</ejb> > </module> > {quote} > (this worked in 2.10.1) > ACTUALLY: > assembly.xml contains reference > {quote}<module> > <ejb>com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar</ejb> > </module> > {quote} > > Due to this difference - JBoss/WildFly cannot deploy the EAR. > (it's easy to reproduce: you may create a ear project from some standard ones > from maven-archetypes and change maven-ear-plugin version to 3.0.0). > > UPDATE: Sorry, maybe it's a bug in M2E-WTP plugin of Eclipse. I tried this > scenario in standalone mode without Eclipse - and assembly.xml is consistent > with the jar files -- This message was sent by Atlassian Jira (v8.3.4#803005)