-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Platform: All, OS: Linux
Hudson does not send failure e-mails when maven fails to validate a pom (easy to
reproduce by using a random text file as a pom).
This might be a maven embedder issue, but the shell command does return 1 (at
least for maven 2.0.8).
(this is on unix, no idea about whether this works on windows)
- is duplicated by
-
JENKINS-2595 Mail is not send
-
- Closed
-
-
JENKINS-1609 when a wrong mvn target is given, build failures are not notified through email
-
- Closed
-
-
JENKINS-1653 E-mail notification fails if check out fails
-
- Closed
-
-
JENKINS-1818 pom parse error doesn't trigger email notification
-
- Closed
-
-
JENKINS-3955 module-pom failures do not trigger mails (was: m2extra-steps stops build failure mails)
-
- Closed
-
I could reproduce this on my debian box also, and I think it is valid on all
platforms. I verified that free-style works with a bad pom.xml.
Steps to reproduce:
1. Create a maven job
2. Build once to get a workspace
3. Create a fake pom.xml in the workspace
4. Build again (with the default pom.xml)
Actual outcome:
Exception stack in output, no email was to sent
Expected outcome:
Exception stack in output and all post build notifications should be executed