|
||||||||
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 Surefire to run tests
a...@bedatadriven.com (JIRA) Thu, 03 Jan 2013 07:03:02 -0800
- [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)
- [JIRA] (JENKINS-8334) maven-plugin insis... a...@bedatadriven.com (JIRA)
- [JIRA] (JENKINS-8334) maven-plugin insis... a...@bedatadriven.com (JIRA)
Could we use a "duck-typing" approach?
Some conventions that could identify test plugins?
That is, a test goal is a maven goal that is called "test", then check for output xml files?
Likewise, if there exists a property testFailureIgnore, then set it to true?