[
https://issues.apache.org/jira/browse/MSTAGE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSTAGE-14.
--------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> DefaultRepositoryCopier rename script does not check move command exit codes
> ----------------------------------------------------------------------------
>
> Key: MSTAGE-14
> URL: https://issues.apache.org/jira/browse/MSTAGE-14
> Project: Maven Stage Plugin
> Issue Type: Improvement
> Affects Versions: 1.0-alpha-2
> Reporter: Francis De Brabandere
> Priority: Major
>
> Only if the last move command fails will the plugin fail. This because the
> exit code for unix scipts is the one from the last command.
> Better would be to use something like this:
> #!/bin/sh
> touch test.txt \
> && rm test.txt \
> && rm test2.txt \ <- fails here and won't continue
> && touch test2.txt \
> rm test2.txt
> this script will fail even if the last 2 commands would succeed (those will
> not even run)
> I know this failing is something that is not common but still possible. We
> actually had this issue and it took quite some time to find out why certain
> builds failed and others not (depended on what the last mv command was).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
