[
https://issues.apache.org/jira/browse/MEAR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453019#comment-16453019
]
Leonid Rozenblyum commented on MEAR-267:
----------------------------------------
Do you mean bundleFileName? It indeed allowed me to provide a possibility to
override the jar name generated itself (so that assembly.xml because
synchronous with the actual jars, this can be considered as related to M2E-WTP).
However dependencies generated by maven-ear plugin have also the 'new' naming
scheme (e.g. com.google.guava-guava-19.0.jar)
while MANIFEST.MF still refers to the default naming. Maybe I miss some
documentation but the new naming scheme causes Manifest refer to incorrect
files.
So if EAR contains EJB which depends on guava, then the EJB manifest contains
the classic classpath.
Do you suggest using <customClasspathLayout> in maven-jar-plugin (actually
maven-archiver-plugin) and override the default naming for manifest?
It looks like a lot of changes must be done to support the new approach then.
> 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
(v7.6.3#76005)
