[ 
https://issues.apache.org/jira/browse/MEAR-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255042#comment-17255042
 ] 

Marat Abrarov commented on MEAR-289:
------------------------------------

[~elharo] and [~hboutemy],

Please take this bug into account when preparing 3.2.0 release. It 
[feels|https://issues.apache.org/jira/browse/MEAR-289?focusedCommentId=17244742&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17244742]
 like this bug is resolved within MEAR-288.

Thank you.

> skinnyWars issue with finalName for Jar module
> ----------------------------------------------
>
>                 Key: MEAR-289
>                 URL: https://issues.apache.org/jira/browse/MEAR-289
>             Project: Maven EAR Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1.0
>            Reporter: Stefan Schmidt
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>         Attachments: maven-ear-example.zip
>
>
> When a finalName is given for a Jar module in a War it is not found by 
> filename @\{artifactId}@-@\{version}@.@\{extension}@ for deletion in 
> maven-ear-plugin.
> Example as attached:
>  * module-jar
>  * module-jar2 (with finalName)
>  * module-war (has jar and jar2 as dependency)
>  * module-ear (has jar as dependency)
> #> ./mvnw clean install
> The module-ear-0-SNAPSHOT.ear contains the 
> com.example-module-war-0-SNAPSHOT.war. In this war both jar's are in folder 
> WEB-INF/lib module-jar-0-SNAPSHOT.jar and module-jar2-0-SNAPSHOT.jar.
> On debugging maven-ear-plugin 3.1.0 it is checking only the finalName.jar and 
> the name com.example-module-jar-0-SNAPSHOT.jar.
> Debugging -> EarMojo.java line 816 to 838
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to