|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) email-ext static-an... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) Aggregated maven re... [email protected] (JIRA)
- [JIRA] (JENKINS-15324) Aggregated maven re... [email protected] (JIRA)

Ok, I see. Then the problem is not in email only. It is in the internal logic of the maven code: the aggregating action is not created when the build failed in a maven module.
Until this is fixed you can use as a workaround the unstable thresholds and not the failed ones (i.e. a warning sets the build to unstable). Alternatively, as you already described use the freestyle project.