maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@codehaus.org>
Subject [jira] (MSTAGE-14) DefaultRepositoryCopier rename script does not check move command exit codes
Date Tue, 03 Feb 2015 10:58:25 GMT

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

Michael Osipov updated MSTAGE-14:
---------------------------------

    Comment: was deleted

(was: 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)

Mime
View raw message