Cloning the issue and re-linking it so it'll show up in release notes for both projects.
Also, the fix for Maven itself to accommodate older plugin-tools-api versions is to leave script source roots relative. This triggered revisions to the following integration tests:
- testForkFromMojo(org.apache.maven.integrationtests.MavenITmng3703ExecutionProjectWithRelativePathsTest)
- testForkFromReport(org.apache.maven.integrationtests.MavenITmng3703ExecutionProjectWithRelativePathsTest)
- testitMNG3475(org.apache.maven.integrationtests.MavenITmng3475BaseAlignedDir)
to make sure the plugin checking the source roots didn't worry about relative script roots.
Cloning the issue and re-linking it so it'll show up in release notes for both projects.
Also, the fix for Maven itself to accommodate older plugin-tools-api versions is to leave script source roots relative. This triggered revisions to the following integration tests:
to make sure the plugin checking the source roots didn't worry about relative script roots.
- testForkFromMojo(org.apache.maven.integrationtests.MavenITmng3703ExecutionProjectWithRelativePathsTest)
- testForkFromReport(org.apache.maven.integrationtests.MavenITmng3703ExecutionProjectWithRelativePathsTest)
- testitMNG3475(org.apache.maven.integrationtests.MavenITmng3475BaseAlignedDir)
to make sure the plugin checking the source roots didn't worry about relative script roots.