Maven Core needs to export the maven-aether-provider artifact so that its components do not get added twice in plugin realm. This happens if the build uses an extension plugin depending on maven-aether-provider, before it was renamed to maven-resolver-provider
Due to the addition of MNG-6229 it turns out that Maven 3.0.5 resolves
optional dependencies differently than other versions. The oldest
version to pass this IT is 3.1.0-alpha-1.
In a locked down environment (no direct Internet connection) these ITs constantly
fail with ArtifactResolutionException. Add dependenies Plexus Utils 2.0.4 and
Maven Settings 2.0 to bootstrap's group 7.
Adds a test for checking that MavenSession.getProjects() contains the
projects being built and that MavenSession.getProjectDependencyGraph()
is set.
The fix for MNG-6173 changed the way these to properties are
initialised. This integration test verifies that the initialisation is
still correct.
Adds a test for checking that MavenSession.getAllProjects() returns the full
list of projects in the reactor even when only some of them are selected
for being built.
This closes#19
o Updated the ITs to correctly detect parent resolution failures. Maven does
not fail the build when it cannot resolve a parent but instead logs a
warning message. The ITs never checked the log to contain the warning messages
but instead asserted the build to fail when a parent cannot be resolved.
The only Maven version supporting parent version ranges is Maven 3.2.2 due to
this.
o Removed an incorrect test case for local parent resolution. Maven ignored
the '<version>' in '<parent>' elements for local parent resolution. The core
has been updated across various versions to eliminate any differences between
local and remote parent resolution. When local parent resolution had been
updated to match remote parent resolution, an existing IT started to fail
testing incorrect behaviour. As soon as the '<parent>' is referenced using a
version range, the '<version>' element in the project becomes mandatory and
does no longer support using an expression any more. This has been that way
for remote parent resolution from day one. It has never been supported to
inherit a version from a parent when referencing that parent using a version
range intentionally.
o Updated to account for updated error messages.
- This will let us fix broken tests while confirming that the versions of Maven that were released using the broken test contain the bug that escaped the broken test
Stephen Connolly
Mario Krizmanic
Karl Heinz Marbaise
Guillaume Boué
Dan Tran
Michael Osipov
Hervé Boutemy
Igor Fedorenko
Christoph Böhme
Christian Schulte
Anton Tanasenko