[
https://issues.apache.org/jira/browse/DERBY-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5461:
---------------------------------
Attachment: derby-5461-01-aa-failBuildOnCommitError.diff
Attaching derby-5461-01-aa-failBuildOnCommitError.diff. This patch causes the
release build to fail if the script trips over an error trying to checkin a
file. Committed at subversion revision 1456937.
> ant release should not continue automatically if svn commit fails
> -----------------------------------------------------------------
>
> Key: DERBY-5461
> URL: https://issues.apache.org/jira/browse/DERBY-5461
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: derby-5461-01-aa-failBuildOnCommitError.diff
>
>
> On my windows system, ant release results in a release.properties file with
> inconsistent line endings. While that may be a problem in itself, what's a
> bigger issue is that the build process attempts to issue svn commit, and when
> that fails, goes on merrily, resulting in a build with a revision number with
> 'M' because there uncommitted changes in the tree.
> There could be other issues resulting in a failed svn commit.
> This could be improved if the build process would halt on failure and e.g.
> prompt for 'a(bort) /c(continue)'. This pause would give the release manager
> a chance to evaluate in another window/shell what's wrong with svn commit and
> possibly resolve manually (including manual svn commit) and continue, or
> start over.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
