[
https://issues.apache.org/jira/browse/MEAR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonid Rozenblyum updated MEAR-267:
-----------------------------------
Description:
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:
<module>
<ejb>tryEar-ejb-1.0-SNAPSHOT.jar</ejb>
</module>
(this worked in 2.10.1)
ACTUALLY:
assembly.xml contains reference
<module>
<ejb>com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar</ejb>
</module>
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).
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
was:
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:
<module>
<ejb>tryEar-ejb-1.0-SNAPSHOT.jar</ejb>
</module>
(this worked in 2.10.1)
ACTUALLY:
assembly.xml contains reference
<module>
<ejb>com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar</ejb>
</module>
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).
Sorry, maybe it's a bug in M2E-WTP plugin of Eclipse. I tried this scenario in
standalone mode without Eclipse - and the build is consistent
> 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:
> <module>
> <ejb>tryEar-ejb-1.0-SNAPSHOT.jar</ejb>
> </module>
> (this worked in 2.10.1)
> ACTUALLY:
> assembly.xml contains reference
> <module>
> <ejb>com.leokom-tryEar-ejb-1.0-SNAPSHOT.jar</ejb>
> </module>
>
> 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).
>
> 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
(v7.6.3#76005)
