[
https://jira.codehaus.org/browse/MEAR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel updated MEAR-177:
-----------------------
Attachment: mear-177.zip
> Jars from previous execution are copied into ear
> ------------------------------------------------
>
> Key: MEAR-177
> URL: https://jira.codehaus.org/browse/MEAR-177
> Project: Maven Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.8
> Reporter: Pavel
> Attachments: mear-177.zip
>
>
> If several executions for ear plugn configured and each contain own jarModule
> than every next execution will contain jar from previous.
> For example following project (see attachment):
> {code}
> root/
> - ear
> - jar1
> - jar2
> {code}
> Ear contain two executions
> {code}
> <execution>
> <id>jar1</id>
> <phase>package</phase>
> <configuration>
> <classifier>jar1</classifier>
> <modules>
> <jarModule>
> <groupId>example</groupId>
> <artifactId>jar1</artifactId>
> </jarModule>
> </modules>
> </configuration>
> <goals><goal>ear</goal></goals>
> </execution>
> <execution>
> <id>jar2</id>
> <phase>package</phase>
> <configuration>
> <classifier>jar2</classifier>
> <modules>
> <jarModule>
> <groupId>example</groupId>
> <artifactId>jar2</artifactId>
> </jarModule>
> </modules>
> </configuration>
> <goals><goal>ear</goal></goals>
> </execution>
> {code}
> But resulting ear-0.0.1-SNAPSHOT-jar2.ear contain both jar1.jar and jar2.jar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
