You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2015/01/31 23:08:18 UTC

[jira] (MSTAGE-14) DefaultRepositoryCopier rename script does not check move command exit codes

     [ https://jira.codehaus.org/browse/MSTAGE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MSTAGE-14.
--------------------------------

    Resolution: Won't Fix

Project has been retired, closing as won't fix.

> DefaultRepositoryCopier rename script does not check move command exit codes
> ----------------------------------------------------------------------------
>
>                 Key: MSTAGE-14
>                 URL: https://jira.codehaus.org/browse/MSTAGE-14
>             Project: Maven Stage Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.0-alpha-2
>            Reporter: Francis De Brabandere
>
> 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
(v6.1.6#6162)