THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Set the Maven prerequisite and dependencies to 3.0, which might cause one or more of the following issues:
- Unknown dependencies in the pom.xml, e.g. the maven-project artifact doesn't exist anymore: its content is now part of maven-core
- CNFE. Some classes have been moved to maven-compat. You could add it temporarily to get it all working again, later you'll get the instructions how to get rid of it.
- Set both the
maven.compiler.source
andmaven.compiler.target
properties to 1.7 - If the project depends on maven-plugin-testing-harness, use version 2.1, since newer versions depend on newer version of Maven dependencies. Ensure to exclude the maven-2.x dependencies which don't exist anymore, e.g. maven-project
- Remove maven-compat (or give it the test-scope if it is required by the maven-plugin-testing-harness)
Maven compat mainly contains business logic which has been moved to Aether. However, we need to support the implementations of both Sonatype (M3.0.x) and Eclipse (M3.1+). The shared component maven-artifact-transfer can select the proper implementation. - Transitive dependencies may still refer to Maven-2.x artifacts, even if they don't exist for Maven 3.x any more: ensure these are excluded. You can enforce this by adding the requireSameVersions enforcer rule to your project.
- Reporting plugins should include org.apache.maven.reporting:maven-reporting-api:3.0
There is a report generated daily with plugins prerequisites.
Housekeeping
While at it, some housekeeping can be done:
...