[
http://jira.codehaus.org/browse/MOJO-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Tran moved MSANDBOX-44 to MOJO-1298:
----------------------------------------
Complexity: Intermediate
Key: MOJO-1298 (was: MSANDBOX-44)
Project: Mojo (was: Maven 2.x Sandbox)
> maven-truezip-plugin: after processing with truezip in package phs.,
> out-of-date resource is installed into repo in install phs.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MOJO-1298
> URL: http://jira.codehaus.org/browse/MOJO-1298
> Project: Mojo
> Issue Type: Bug
> Environment: Windows XP, Maven 2.0.9, maven-truezip
> 1.0-beta-1-SNAPSHOT
> Reporter: Rasto Cesnek
>
> In the <build> section, I use truzip plugin bound to package phase to
> manipulate a large archive (a 12M SAR file) to remove unwanted stuff from the
> packaging (remove **/META-INF/maven/ directories from dependent JARs, etc.).
> When I ran "mvn clean install", the plugin scans the SAR file during the
> package phase. Then the install phase follows. When the build finishes, the
> SAR file in the /target folder is correct - all META-INF/maven directories
> removed. How ever, the file which is installed during the install phase IS
> NOT CORRECT, it still contains all the META-INF/maven directories in it. When
> observing the behavior closely, it looks like the file manipulated by truezip
> is NOT YET UPDATED on the file system, when the install phase runs. It seems,
> that it gets updated after the install pahse finishes - shortly before the
> entire maven build finishes.
> The expected behavior would be, that the file processed by truezip lands in
> the repo after install.
> Is this connected to OS (Windows XP) and some file cacheing? May it have
> something to do with the file size? A threading problem?
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>truezip-maven-plugin</artifactId>
> <version>1.0-beta-1-SNAPSHOT</version>
> <executions>
> <execution>
> <!-- Remove META-INF/maven s from embedded archives,
> JBoss 3.2.8 has digestive problems with them and then
> pukes incomplete deployment messages. -->
> <id>remove maven metas from jars</id>
> <goals>
> <goal>remove</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <fileset>
>
> <directory>${project.build.directory}/${project.build.finalName}.sar/</directory>
> <includes>
>
> <include>**/META-INF/maven/</include>
> </includes>
> </fileset>
> <verbose>true</verbose>
> </configuration>
> </execution>
> </executions>
> </plugin>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
