|
||||||||
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-8334) maven-plugin insists on... a...@bedatadriven.com (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... a...@bedatadriven.com (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... a...@bedatadriven.com (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... jwb...@gmail.com (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... a...@bedatadriven.com (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... jwb...@gmail.com (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... a...@bedatadriven.com (JIRA)
> Why not just check for junit xml files after all the plugins have executed?
That's just not how the Maven jobs work and it would mean a major refactoring to change that - and I'm not even positive that this is a desirable change.