[
https://jira.codehaus.org/browse/MEAR-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348035#comment-348035
]
David Hoffer commented on MEAR-189:
-----------------------------------
There isn't any errors generated in the logs to report. It builds the
artifacts in the correct location. The problem is the contents of the produced
artifacts is incorrect. When using the skinnyWars option what that is supposed
to do is:
Move specified jars (1) from war to ear's lib folder (2) & update the war's
Manifest (3) so that it now references those jars in the ear's lib folder.
The problem is that it does not do item 1 above...it copies the jars to the
ear's lib...it never removes them from the war at all.
Just check the wars in the ear...they should not have the jars that have been
put in the ear's lib folder but they still have all the original jars.
> fileNameMapping set to no-version breaks skinnyWars feature
> -----------------------------------------------------------
>
> Key: MEAR-189
> URL: https://jira.codehaus.org/browse/MEAR-189
> Project: Maven Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.7, 2.8, 2.9
> Reporter: David Hoffer
>
> I have my plugin configured as:
> <plugin>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.9</version>
> <configuration>
> <defaultJavaBundleDir>lib/</defaultJavaBundleDir>
> <skinnyWars>true</skinnyWars>
> <fileNameMapping>no-version</fileNameMapping>
> </configuration>
> </plugin>
> And the inclusion of <fileNameMapping>no-version</fileNameMapping> which I
> need, causes all the wars to fat.
> Is this a known bug? This is a major problem for me, is there any workaround?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
