Thanks, Brett! As it turns out, the place we were seeing this happened
to be with Maven 2.0.7 on a Windows machine. We've upgraded it just
today. So, we'll keep an eye out on our next release.
Dave
Brett Porter wrote:
My only guess would be on Windows there may be a case were the nested
run fails but the primary run doesn't detect it, but only under Maven
2.0.7 or if certain env vars are set.
If the nested build is succeeding, then the deployment is either not
attempted or the wrong response code is coming back.
- Brett
On 23/12/2008, at 4:45 AM, David C. Hicks wrote:
I'm afraid I don't have a test case in-hand at this time, but I
wanted to ask the community. Is there a known problem with
maven-release-plugin reporting a false successful build? I didn't see
anything that seemed to indicate that in JIRA. My team has noticed a
couple of events in which we had such things happen. I *think* it
occurs in the release:perform phase - if the file fails to deploy to
our Nexus repository, we still see the final outcome of the Maven
call as successful. We'll try to keep an eye out for it and hopefully
create a test case, but if anyone knows of something like this I'd
really appreciate a knowledge dump.
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
