The Apache Maven team is pleased to announce the release of the Apache Maven Shared Maven Invoker, version 2.2
This API is concerned with firing a Maven build in a new JVM. It accomplishes its task by building up a conventional Maven command line from options given in the current request, along with those global options specified in the invoker itself. Once it has the command line, the invoker will execute it, and capture the resulting exit code or any exception thrown to signal a failure to execute. Input/output control can be specified using an InputStream and up to two InvocationOutputHandlers.
Important message for Windows users who want to invoke Apache Maven 3.3.1 and above:
Due to http://jira.codehaus.org/browse/MNG-5776 the start-script has been renamed from mvn.bat to mvn.cmd, which caused the previous versions of Maven Invoker to not being able to find the executable file anymore. This critical issue has been fixed in this release.
In the next release of the maven-invoker-plugin, which should be released soon, we’ll add this fix as well. In the meantime you can configure the plugin like this:
1 2 3 4 5 6 7 8 9 10 11 12
- MSHARED-261 – DefaultInvoker does not set M2_HOME
- MSHARED-278 – NullPointerException in MavenCommandLineBuilder
- MSHARED-411 – maven-invoker – addShellEnvironment forgets variable settings on successive calls
- MSHARED-358 – Update version of plexus-utils to 3.0.15
- MSHARED-371 – Increase chance of java8 compliance by updating to plexus-component-* 1.6
- MSHARED-379 – Upgrade plexus-utils to 3.0.20
- MSHARED-413 – Invoker fails on Windows since Maven-3.3.x
- MSHARED-414 – Upgrade to JUnit4
-The Apache Maven team