There is a problem in maven-plugin-testing-harness I meant to fix right
after I released 2.0 but it somehow slipped my mind.

Use of scope=compile for maven core dependencies can result in rather
hard to debug problems if plugin being tested specifies different
version of maven in its pom.xml. I think maven-plugin-testing-harness
should scope=provide for all its maven core dependencies, see attached diff.

Is this something we can include in 2.1?

--
Regards,
Igor

On 12-09-22 4:15 PM, Kristian Rosenvold wrote:
I'd like to release maven plugin testing 2.1

The main intent of this release is to modernize dependencies, so we
can build on post 1.5 jdks for dependant projects.

This includes especially upgrading to easymock 2.5.2, dependencies
updating to this version should
adjust their easymock dependency accordingly since there is little isolation.

We solved no issues

There are still a few issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=MPLUGINTESTING&status=1


Staging repo:
https://repository.apache.org/content/repositories/maven-021/

Staging site:
http://maven.apache.org/plugin-testing/maven-plugin-testing-2.1/plugin-testing/

Relative links appear off for staged sites, so here are links for
modules documentation

http://maven.apache.org/plugin-testing/maven-plugin-testing-harness-2.1/plugin-testing/maven-plugin-testing-harness/
http://maven.apache.org/plugin-testing/maven-plugin-testing-tools-2.1/plugin-testing/maven-plugin-testing-tools/
http://maven.apache.org/plugin-testing/maven-test-tools-2.1/plugin-testing/maven-test-tools/


Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Index: pom.xml
===================================================================
--- pom.xml     (revision 1388950)
+++ pom.xml     (working copy)
@@ -152,38 +152,45 @@
         <groupId>org.apache.maven</groupId>
         <artifactId>maven-core</artifactId>
         <version>${mavenVersion}</version>
+        <scope>provided</scope>
       </dependency>
       <dependency>
         <groupId>org.apache.maven</groupId>
         <artifactId>maven-compat</artifactId>
         <version>${mavenVersion}</version>
+        <scope>provided</scope>
       </dependency>
       <dependency>
         <groupId>org.apache.maven</groupId>
         <artifactId>maven-model</artifactId>
         <version>${mavenVersion}</version>
+        <scope>provided</scope>
       </dependency>
       <dependency>
         <groupId>org.apache.maven</groupId>
         <artifactId>maven-plugin-api</artifactId>
         <version>${mavenVersion}</version>
+        <scope>provided</scope>
       </dependency>    
       <dependency>
         <groupId>org.apache.maven</groupId>
         <artifactId>maven-aether-provider</artifactId>
         <version>${mavenVersion}</version>
+        <scope>provided</scope>
       </dependency>    
     
       <dependency>
         <groupId>org.codehaus.plexus</groupId>
         <artifactId>plexus-utils</artifactId>
         <version>3.0.8</version>
+        <scope>provided</scope>
       </dependency>    
     
       <dependency>
         <groupId>junit</groupId>
         <artifactId>junit</artifactId>
         <version>4.10</version>
+        <scope>provided</scope>
       </dependency>    
     </dependencies>
   </dependencyManagement>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to