Does this mean we have now officially caved in and dropped surefire 1.3
support ? (Looking for champagne bottle)
Kristian
Den 05.08.2010 14:15, skrev Stephen Connolly:
I can roll it back out.... just wanted to ensure that because I was
specifying the requirements that they would be stated on the site
On 5 August 2010 13:13, Benjamin Bentmann<benjamin.bentm...@udo.edu> wrote:
Hi Stephen,
Author: stephenc
Date: Thu Aug 5 12:03:07 2010
New Revision: 982558
URL: http://svn.apache.org/viewvc?rev=982558&view=rev
Log:
SUREFIRE-623 finessing
Modified:
maven/surefire/trunk/maven-failsafe-plugin/pom.xml
maven/surefire/trunk/maven-surefire-plugin/pom.xml
maven/surefire/trunk/maven-surefire-report-plugin/pom.xml
Modified: maven/surefire/trunk/maven-failsafe-plugin/pom.xml
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/pom.xml?rev=982558&r1=982557&r2=982558&view=diff
==============================================================================
--- maven/surefire/trunk/maven-failsafe-plugin/pom.xml (original)
+++ maven/surefire/trunk/maven-failsafe-plugin/pom.xml Thu Aug 5 12:03:07
2010
@@ -244,6 +244,7 @@
<version>2.6</version>
<configuration>
<requirements>
+<maven>2.0.9</maven>
<jdk>1.4</jdk>
</requirements>
</configuration>
Why exactly is this duplication needed given the plugins have
<prerequisites> on the Maven version?
Benjamin
