[
http://jira.codehaus.org/browse/MRELEASE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103062
]
William Ferguson commented on MRELEASE-270:
-------------------------------------------
NB the attached zip contains a project with uncompilable source.
> release:prepare doesn't fail when the project it is building fails to compile
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-270
> URL: http://jira.codehaus.org/browse/MRELEASE-270
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Reporter: William Ferguson
> Attachments: MRELEASE-XXX.zip
>
>
> Unusual situation on our build server, where one of the dependent libraries
> had been corrupted in its local repository.
> 'mvn compile' would fail with compilation errors - it couldn't find the
> classes from the corrupt jar.
> 'mvn release:prepare' would note compilation errors and indicate build
> failure, but would continue on with the release, modify the POMs, tag the
> source and finally complete indicating success.
> I noted that the same thing can happen if uncompilable source is checked in,
> though at least then you would get the compilation failure on your local
> machine too.
> I think release:prepare should clearly fail (it wasn't clear in this instance
> unless you scrolled back through the build output) if any part of the
> release:prepare fails.
> To replicate either
> a) Attempt top release uncompilable code.
> b) Replace a dependent jar with a renamed text file and attempt to release.
--
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
