Commits on Jun 9, 2017
  1. [MNG-6240] Duplicate components in plugin extension realm when plugin…

    … depends on maven-aether-resolver
    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
    Guillaume Boué committed Jun 9, 2017
Commits on May 24, 2017
  1. [MNG-6084] Support JSR 250 annotations

    Dan Tran committed with michael-o Sep 12, 2016
Commits on May 13, 2017
  1. Expect fail for MNG-947 with Maven 3.0.5

    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.
    michael-o committed May 13, 2017
Commits on May 10, 2017
Commits on May 9, 2017
  1. [MNG-6229] Write out optionality in Core IT Plugins for collection an…

    …d resolution
    Write out " (optional)" in the log entry as well as to the file for later
    michael-o committed May 9, 2017
Commits on May 7, 2017
  1. MNG-6210 shortened test project file names

    Signed-off-by: Igor Fedorenko <>
    ifedorenko committed May 7, 2017
Commits on Apr 14, 2017
  1. MNG-6210 allow maven custom guice scopes in .mvn/extensions

    Signed-off-by: Igor Fedorenko <>
    ifedorenko committed Apr 13, 2017
Commits on Apr 13, 2017
  1. MNG-6209 better executeMojo thread context classloader

    Signed-off-by: Igor Fedorenko <>
    ifedorenko committed Apr 11, 2017
Commits on Apr 9, 2017
  1. Fix ITs MNG-5019 and MNG-5224 with ArtifactResolutionException

    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.
    michael-o committed Apr 9, 2017
Commits on Apr 5, 2017
Commits on Apr 4, 2017
Commits on Apr 3, 2017
  1. added bootstrap info

    hboutemy committed Apr 3, 2017
  2. fix markdown link

    stephenc committed Apr 3, 2017
  3. More test environments

    stephenc committed Apr 3, 2017
Commits on Apr 2, 2017
Commits on Apr 1, 2017
  1. [MNG-6202] Cannot pass nonProxyHosts to ITs making remote tests lock …

    …up when proxy rejects to proxy internal hosts
    Set default value 'localhost' of 'proxy.nonProxyHosts' and allow users to
    override if necessary.
    michael-o committed Apr 1, 2017
Commits on Mar 31, 2017
Commits on Mar 25, 2017
Commits on Mar 19, 2017
Commits on Mar 13, 2017
  1. [MNG-6057], [MNG-6090], [MNG-5895]

     o Added IT's for MNG-5895, MNG-6057, MNG-6090
     o Added flatten-maven-plugin for usage during
       the IT's.
    khmarbaise committed Mar 7, 2017
Commits on Mar 6, 2017
  1. [MNG-6173] Test getProjects() and getProjectDependencyGraph()

    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.
    cboehme committed with ChristianSchulte Mar 4, 2017
  2. [MNG-6173] getAllProjects() should return all projects

    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
    cboehme committed with ChristianSchulte Mar 3, 2017
Commits on Feb 24, 2017
  1. 3.5.0-alpha-1 < 3.5.0

    stephenc committed Feb 24, 2017
Commits on Feb 14, 2017
Commits on Feb 10, 2017
  1. [MNG-2199] Support version ranges in parent elements

    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
    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.
    ChristianSchulte committed Dec 12, 2015
Commits on Feb 4, 2017