[
http://jira.codehaus.org/browse/MANTRUN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated MANTRUN-119:
------------------------------
Fix Version/s: 1.5
Assignee: Paul Gier
> copy task does not respect failonerror=false
> --------------------------------------------
>
> Key: MANTRUN-119
> URL: http://jira.codehaus.org/browse/MANTRUN-119
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Maven 2.2.1,
> jRockit (Java 6)
> Reporter: René Zanner
> Assignee: Paul Gier
> Priority: Blocker
> Fix For: 1.5
>
>
> When defining a copy task, the antrun plugin propagates it's failure although
> "failonerror" is set to true: the maven build stops.
> In my case I try to copy a file which does not exist in some maven build
> situations. The build should not fail but try to copy a different file
> instead. With antrun 1.2 it still works (the build continues with the next
> copy task), but with the current version the build fails.
> <configuration>
> <tasks>
> <!-- in single project builds, the file to be copied has a different
> name - reactor build with antrun 1.3 fails here, though failonerror is false!
> -->
> <copy file="${project.build.directory}/dependency/model.xml"
> tofile="${project.build.directory}/model.xml" overwrite="true" verbose="true"
> failonerror="false" />
> <!-- in rector builds, the name of the file contains the correct
> maven type (xmi) and the version number -->
> <copy
> file="${project.build.directory}/dependency/model-${project.version}.xmi"
> tofile="${project.build.directory}/model.xml" overwrite="true" verbose="true"
> failonerror="false" />
> </tasks>
> </configuration>
--
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
