The Apache Maven team is pleased to announce the release of the Apache Maven 3.6.2.

Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project’s build, reporting and documentation from a central piece of information.

You can find out more about Apache Maven at https://maven.apache.org

You can download the appropriate sources etc. from the download page

We really value the contributions of these non committers, so this section is focused on those individuals. Descriptions of the issues fixed can be found at the end of these release notes.

Issue Reporters of this release:

• Benoit GUERIN
• Christian Schulte
• Elliotte Rusty Harold
• Falko Modler
• Francesco Chicchiriccò
• Guillaume Nodet,
• guofei
• Joseph Walton
• Louis Mills
• Mark Derricutt,
• Mark McKelvy
• Mickael Istria
• Nicolas Echegut
• Nicolas Radde
• Raphael Rösch
• Ray Tsang
• Robert Thornton
• Rohan Padhye
• Sergey Chernov
• Stefan Oehme
• Thibaud Lepretre
• zhb.

Code Contributors of this release:

• Guillaume Nodet
• Mickael Istria
• Ray Tsang
• Stefan Oehme
• Joseph Walton
• Bo Zhang
• AElMehdi
• Christian Schulte
• Mao Shuai
• MartinKanters
• Sergey Chernov
• Jesse Glick.

Many thanks to all reporters and contributors for their time and support.

(Please send an email to the dev list if we missed one to mention).

Known Issues

None.

Overview about the changes

• This release focuses mostly performance improvements, better memory footprint, and less CPU usage.

• We are continuing to convert Maven Core to use JSR 330 annotations instead of Plexus (still not finished, see MNG-5577).

• New support for ‘release’ qualifier (see MNG-6655).

• The toolchain.xml file supports environment variables (see MNG-6665).

User visible Changes

toolchain.xml now supports usage of environment variables which looks like this:

1
2
3
4
5
6
7
8
9
10

<toolchain>
    <type>jdk</type>
    <provides>
      <version>1.8</version>
      <vendor>sun</vendor>
    </provides>
    <configuration>
  <jdkHome>${env.JDK_HOME_8}</jdkHome>
    </configuration>
</toolchain>

The detailed issue list

Bugs:

• MNG-6375 – NullPointerException when pom.xml has incomplete XML tag
• MNG-6626 – NullPointerException in DefaultExceptionHandler
• MNG-6629 – DefaultModelValidator.validateId is inefficient
• MNG-6630 – ComparableVersion.parseVersion is inefficient
• MNG-6631 – DefaultArtifactVersion.parseVersion is inefficient
• MNG-6632 – ArtifactHandlerManager.getArtifactHandler is inefficient
• MNG-6633 – ExcludesArtifactFilter is a memory hog
• MNG-6636 – NPE on reporting convertion (DefaultReportingConverter) when inheritance of with no reports
• MNG-6639 – Child inherit.append.path attributes not defined in Maven POM XSD
• MNG-6642 – Tycho-based modules do not build with 3.6.1 (works with 3.6.0)
• MNG-6643 – Version comparison CLI does not work anymore
• MNG-6644 – NPE in DefaultReportingConverter when reports has no InputLocation (using polyglot Maven)
• MNG-6647 – NPE in DefaultReportingConverter (when reports injected by Repaint IO maven-tiles)
• MNG-6653 – DefaultProjectBuildingRequest copy constructor does not copy all fields
• MNG-6668 – Model location handling uses too much memory
• MNG-6669 – Tycho cannot resolve project dependencies
• MNG-6700 – Equal compile source roots are added multiple times
• MNG-6703 – DefaultUrlNormalizer doesn’t normalize all relative URIs
• MNG-6704 – MavenRepositorySystemUtils.newSession() misses assignment
• MNG-6707 – Maven XML parser does not accept ‘>’ in XML processing instructions
• MNG-6712 – Downgrade maven-resolver:1.4.0 to 1.3.3
• MNG-6713 – Fix ExclusionArtifactFilter to respect wildcard
• MNG-6716 – relative testSourceDirectory on macos throw duplicate class error
• MNG-6720 – MultiThreadedBuilder: wait for parallel running projects when using —fail-fast
• MNG-6723 – MavenProject.getParentFile() not set when using ProjectBuilder.build(List, …)

Improvements

• MNG-6069 – Migrate to non deprecated parts of Commons CLI
• MNG-6638 – Prevent reparsing POMs in MavenMetadataSource
• MNG-6655 – Add support for “release” qualifier
• MNG-6665 – toolchain.xml file should support environment variables
• MNG-6667 – Hint at Maven upgrade requirement when trying to build a pom.xml with a newer modelVersion
• MNG-6675 – Make Resolver debug log messages for projects and plugins consistent
• MNG-6695 – Improve speed in collection merging
• MNG-6696 – Speed improvements while parsing big reactor projects
• MNG-6697 – Add a fast interpolator not using reflection
• MNG-6698 – Lazily compute the ManagedVersionMap
• MNG-6701 – Document maven.repo.local system property
• MNG-6702 – Improve DefaultModelValidator performance
• MNG-6705 – Speep up Artifact version check and Parent interpolation
• MNG-6718 – Upgrade Plexus Utils to 3.2.1
• MNG-6729 – StringSearchModelInterpolator introspects objects from Java API
• MNG-6747 – Generalize ‘resume from’ message when build reactor fails

Test

• MNG-6535 – Improve test coverage of org.apache.maven.model.path.DefaultUrlNormalizer

Wish

Task

• MNG-6681 – improve documentation: dependency type = file classifier(optional)+extension + additional hints on dependency features

Dependency upgrade

• MNG-6549 – Remove unused transitive dependencies of Guava
• MNG-6627 – upgrade plexus-component-metadata to 2.0.0 to get reproducible META-INF/plexus/components.xml
• MNG-6646 – Upgrade maven-assembly-plugin to 3.1.1
• MNG-6671 – Upgrade Modello to 1.11
• MNG-6674 – Upgrade Wagon to 3.3.3
• MNG-6738 – Upgrade maven-resolver to 1.4.1

Sub Tasks

• MNG-6680 – Convert Maven Settings Builder to JSR 330
• MNG-6685 – Convert Maven Model Builder to JSR 330
• MNG-6686 – Convert Maven Embedder to JSR 330

The full list of changes can be found in our issue management system.

Complete Release Notes

See complete release notes for all versions

• The Apache Maven Team.

The Apache Maven team is pleased to announce the release of the Doxia Site Tools Version 1.9, Released

Doxia Sitetools is an extension of base Doxia component that generates either HTML sites, consisting of decoration and content that was generated by Doxia, or documents like RTF or PDF.

Release Notes – Maven Doxia base – Version 1.9

You can download the appropriate sources etc. from the download page.

Release Notes – Maven Doxia Sitetools – Version 1.9

Bugs:

• DOXIA-497 – APTSink: links and paragraphs inside tables
• DOXIA-538 – Tag used for monospaced is not a valid html5 tag
• DOXIA-567 – update dependency schema: pegdown not used any more but flexmark-java
• DOXIA-570 – Unescaped links in xml based figureGraphics elements
• DOXIA-577 – Handle whitespace in tables properly in ConfluenceSink
• DOXIA-578 – Boxed verbatim sections uses incorrect Confluence syntax
• DOXIA-579 – Lists in Confluence syntax requires 2 line breaks after the list
• DOXIA-581 – Provide a usable output implementation for definition lists
• DOXIA-582 – Text within a monospace block need to escape characters with special meaning in Confluence
• DOXIA-583 – XhtmlBaseSink: Table caption is escaped incorrectly

New Feature:

• DOXIA-584 – Support rewriting multiple page documentation crosslinks from .md to .html

Improvements:

• DOXIA-409 – Upgrade to Apache FOP 2.2 (was 1.0)
• DOXIA-528 – Enable rendering of HTML5 data- attributes
• DOXIA-575 – Add support for (X)HTML5
• DOXIA-585 – Propagate macro related exceptions to caller in xhtml parser
• DOXIA-587 – Maven site generate invalid link with markdown

Tasks:

• DOXIA-586 – Removed unused properties and cleaned up pom file
• DOXIA-591 – Require minimum Java 7 at runtime

Dependency upgrades:

• DOXIA-572 – Upgrade parent to 32
• DOXIA-576 – Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient)
• DOXIA-592 – Upgrade Markdown parser – flexmark-java to 0.42.8
• DOXIA-593 – Upgrade to Apache FOP 2.3

Enjoy,

-The Apache Maven team

The Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 3.1.0.

The Checkstyle Plugin generates a report regarding the code style used by the developers. For more information about Checkstyle, see http://checkstyle.sourceforge.net/.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-checkstyle-plugin</artifactId>
  <version>3.1.0</version>
</plugin>

Release Notes – Apache Maven Checkstyle Plugin – Version 3.1.0

You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-checkstyle-plugin/download.cgi

Bugs:

• MCHECKSTYLE-323 – usage of checkstyle 7.0 (jdk8 is required)
• MCHECKSTYLE-344 – StringIndexOutOfBoundsException in RuleUtil
• MCHECKSTYLE-347 – StringIndexOutOfBoundsException when checkstyle.violation.ignore set to empty value
• MCHECKSTYLE-365 – Site Report, Rules: Violation count incorrect for duplicate rules when one uses default severity

Improvements:

• MCHECKSTYLE-326 – Running mvn install works first time second it does not
• MCHECKSTYLE-350 – Lock version of animal-sniffer-maven-plugin
• MCHECKSTYLE-353 – Don’t resolve any dependencies
• MCHECKSTYLE-374 – Replace deprecated methods in Checkstyle
• MCHECKSTYLE-375 – Upgrade all test XML doctypes

Dependency upgrades:

• MCHECKSTYLE-349 – Upgrade to parent pom 31
• MCHECKSTYLE-359 – Upgrade maven-plugins parent to version 32
• MCHECKSTYLE-360 – Upgrade maven-site-plugin to 3.7.1 for integration tests
• MCHECKSTYLE-366 – Upgrade checkstyle to a more recent version

Enjoy,

-The Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven WAR Plugin, version 3.2.3.

The WAR Plugin is responsible for collecting all artifact dependencies, classes and resources of the web application and packaging them into a web application archive.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-war-plugin</artifactId>
  <version>3.2.3</version>
</plugin>

You can download the appropriate sources etc. from the download page.

Important Note:

• Maven 3.X only
• JDK 7 minimum requirement

Release Notes – Maven WAR Plugin – Version 3.2.3

Bug:

• MWAR-371 – Overlays break first-win rule for web resource with target path ending with ‘/’

Dependency upgrades:

• MWAR-419 – Upgrade maven-plugins parent to version 32
• MWAR-423 – Upgrade plexus-archiver to 4.1.0
• MWAR-424 – Upgrade maven-archiver to 3.4.0
• MWAR-425 – Upgrade plexus-utils to 3.2.0

Many thanks to all reporters/contributors/testers of this release.

Voters:

• Francois Papon
• Eric Lilja
• Gabriel Belingueres

Enjoy,

-The Apache Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven Source Plugin, Version 3.1.0.

The Source Plugin creates a jar archive of the source files of the current project. The jar file is, by default, created in the project’s target directory.

Important Note:

• Maven 3.X only
• JDK 7 minimum requirement

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-source-plugin</artifactId>
  <version>3.1.0</version>
</plugin>

You can download the appropriate sources etc. from the download page.

Release Notes – Apache Maven Source Version 3.1.0

Bugs:

• MSOURCES-105 – Remove link to non-existing Codehaus wiki
• MSOURCES-108 – Remove the readonly=true from finalName
• MSOURCES-119 – Archiving to jar is very slow

Improvement:

• MSOURCES-110 – Add IT to prevent readonly=true problem with parameter

Dependency upgrades:

• MSOURCES-109 – Upgrade parent to 31
• MSOURCES-111 – Upgrade maven-archiver / plexus-archiver
• MSOURCES-112 – Upgrade plexus-utils 3.1.0
• MSOURCES-114 – Upgrade mave-surefire/failsafe-plugin 2.21.0
• MSOURCES-116 – Upgrade plexus-archiver to 3.6.0
• MSOURCES-117 – Upgrade maven-plugins parent to version 32
• MSOURCES-118 – Upgrade JUnit to 4.12

Enjoy,

-The Apache Maven team

Karl Heinz Marbaise

The Apache Maven team is pleased to announce the release of the Apache Maven Jar Plugin, version 3.1.2.

This plugin provides the capability to build jars.

Important Note:

• Maven 3.X only
• JDK 7 minimum requirement

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-jar-plugin</artifactId>
  <version>3.1.2</version>
</plugin>

Release Notes – Maven JAR Plugin – Version 3.1.2

Bug:

• MJAR-259 – Archiving to jar is very slow

Improvement:

• MJAR-238 – Allow setting of module main class

Enjoy,

• The Apache Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven Surefire Plugin, version 2.22.2.

The release contains 17 bug fixes. Again we received contributions from the community in form of bug reports and bug fixes. Thank you and keep them coming!

You should specify the version in your project’s plugin configuration:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>2.22.2</version>
</plugin>

or for failsafe:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-failsafe-plugin</artifactId>
  <version>2.22.2</version>
</plugin>

or for surefire-report:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-report-plugin</artifactId>
  <version>2.22.2</version>
</plugin>

Release Notes – Maven Surefire – Version 2.22.2

Bugs:

• SUREFIRE-1614– JUnit Runner that writes to System.out corrupts Surefire’s STDOUT when using JUnit’s Vintage Engine

Enjoy,

-The Apache Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven Compiler Plugin, version 3.8.1.

The Compiler Plugin is used to compile the sources of your project.

Important Notes since Version 3.8.1

• The default value for source/target has been lifted from 1.5 to 1.6 see MCOMPILER-335.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-compiler-plugin</artifactId>
  <version>3.8.1</version>
</plugin>

Release Notes – Maven Compiler Plugin – Version 3.8.1

Bugs:

• MCOMPILER-306 – Incorrect compilerArgs example usage
• MCOMPILER-349 – maven-compiler-plugin does not recompile a module if a dependency module has been updated & recompiled
• MCOMPILER-360 – NPE when calculating modulepath with invalid entries
• MCOMPILER-379 – Fatal error compiling: basedir … arget/generated-sources/annotations does not exist

Improvements:

• MCOMPILER-322 – Set the JPMS module version
• MCOMPILER-366 – Warning about automodules should provide the list of offending libraries

Enjoy,

• The Apache Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven Archetype Plugin, version 3.1.0.

In short, Archetype is a Maven project templating toolkit. An archetype is defined as an original pattern or model from which all other things of the same kind are made. The names fits as we are trying to provide a system that provides a consistent means of generating Maven projects. Archetype will help authors create Maven project templates for users, and provides users with the means to generate parameterized versions of those project templates.

https://maven.apache.org/archetype/maven-archetype-plugin/index.html

You should specify the version in your project’s plugin configuration:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-archetype-plugin</artifactId>
  <version>3.1.0</version>
</plugin>

You can download the appropriate sources etc. from the download page.

[Release Notes – Maven Archetype Plugin – Version 3.1.0]

Bugs:

• ARCHETYPE-492 Underscore in filenames problematic due to greedy regex
• ARCHETYPE-530 [archetype:create-from-project] Proxy configuration from settings.xml is not taken into account
• ARCHETYPE-534 archetype-descriptor.xsd is out of date

New Features:

• ARCHETYPE-553 Allow additional properties for IntegrationTestMojo’s MavenInvoker
• ARCHETYPE-554 create archetype-descriptor-1.1.0.xsd containing validation regexp

Improvements:

• ARCHETYPE-536 Update Groovy dependency and enable Groovy Grape in archetype-post-generate.groovy script (by including Ivy dependency)
• ARCHETYPE-560 Require Java 7

Task:

• ARCHETYPE-542 switch from Git-WIP to Gitbox

Dependency upgrades:

• ARCHETYPE-543 Upgrade modello from 1.8.3 to 1.9.1
• ARCHETYPE-544 Upgrade mave-surefire/failsafe-plugin 2.21.0
• ARCHETYPE-545 Upgrade parent to 33
• ARCHETYPE-551 Upgrade maven-invoker to 3.0.1
• ARCHETYPE-557 Upgrade surefire to 2.22.1

Enjoy,

-The Apache Maven team

The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.12.0

A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics.

You can download the appropriate sources etc. from the download page.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-pmd-plugin</artifactId>
  <version>3.12.0</version>
</plugin>

Release Notes – Apache Maven PMD Plugin – Version 3.12.0

Bugs:

• MPMD-277 – Plugin tries to download local submodules from repo

New Features:

• MPMD-280 – Support targetJdk 12
• MPMD-281 – Display found violations grouped by priority

Improvements:

• MPMD-279 – Improve documentation of maxAllowedViolations
• MPMD-282 – Add rule name to HTML report

Dependency upgrades:

• MPMD-275 – Upgrade to PMD 6.13.0
• MPMD-284 – Upgrade parent to 33

Enjoy,

-The Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven Help Plugin, version 3.2.0

The Maven Help Plugin is used to get relative information about a project or the system. It can be used to get a description of a particular plugin, including the plugin’s goals with their parameters and component requirements, the effective POM and effective settings of the current build, and the profiles applied to the current project being built.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-help-plugin</artifactId>
  <version>3.2.0</version>
</plugin>

You can download the appropriate sources etc. from the download page.

Release Notes – Maven Help Plugin – Version 3.2.0

New Feature:

• MPH-160 – help:effective-pom -Dverbose: add source location as comments in effective pom.xml

Improvement:

• MPH-161 – add color to goal or plugin description

Enjoy,

-The Apache Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven 3.6.1.

Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project’s build, reporting and documentation from a central piece of information.

You can find out more about Apache Maven at https://maven.apache.org

You can download the appropriate sources etc. from the download page

We really value the contributions of these non committers, so this section is focused on those individuals. Descriptions of the issues fixed can be found at the end of these release notes.

Issue Reporters of this release:

• MNG-5705 Ondra Žižka
• MNG-5965 Matthias Schmalz
• MNG-6059 Andreas Sewe
• MNG-6159 Christian Aistleitner
• MNG-6213 Jin Kwon
• MNG-6256 Christoph Etzel
• MNG-6261 Dawid Weiss
• MNG-6262 Gene Smith
• MNG-6346 Patrik Jetzer
• MNG-6374 Rohan Padhye
• MNG-6495 Elliotte Rusty Harold
• MNG-6506 Andreas Veithen
• MNG-6526 Olaf Otto
• MNG-6529 Michael Istria
• MNG-6530 Michael Istria
• MNG-6533 Michael Istria
• MNG-6543 Romain Manni-Bucau
• MNG-6558 Guy Brand
• MNG-6577 Rohan Padhye
• MNG-6591 Olaf Otto
• MNG-6605 Gunnar Wagenknecht
• MNG-6618 Viacheslav Yakunin

Code Contributors of this release:

• MNG-6374 Gabriel Belingueres (indirectly via plexus-utils PR)
• MNG-6529 Michael Istria
• MNG-6530 Michael Istria
• MNG-6558 Guy Brand
• MNG-6261 Fabiano C. de Oliveira
• MNG-6533 Michael Istria

Many thanks to all reporters and contributors for their time and support.

(Please send an email to the dev list if we missed one to mention).

Preliminary Testers

Thanks to the following preliminary testers:

• Gabriel Belingueres
• Francois Papon
• Eric Lilja

Known Issues

If you are using Maven reporting, it might happen that you will get an exception which looks like this:

1
2
3
4
5
6
7
8

[INFO] Scanning for projects...
[ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
...
Caused by: java.lang.NullPointerException
    at org.apache.maven.model.plugin.DefaultReportingConverter.convert (DefaultReportingConverter.java:243)
...

This is caused by using a <reportSet>..</reportSet> which does not contain a <report></report> element.

Temporarily this issue can circumvented by adding an empty <report></report> element inside the <reportSet></reportSet>.

An issue has been created to track the fix.

Overview about the changes

• An issue has been fixed causing multiple executions of plugin goals, related to using parallel build options like mvn plugin:goal -T 4. This resulted in duplicated executions of phases. This has been fixed with MNG-5965.

• NullPointerException related to call in parallel build like mvn -T 1C clean javadoc:aggregate MNG-5705

• A performance issue related to artifact transfer has been found related to WAGON-537. It has been solved via the update to Maven Wagon 3.3.1.

• There had been issues related calling Maven script like this: mvn -f ..

  • Having parentheses within the path, which has been fixed with MNG-6346.
  • Script can break having special characters as part of the path, which has been solved with MNG-6256.

• Issue related to the Maven Resolver API which broke some IDEs (for example https://youtrack.jetbrains.com/issue/IDEA-201282); this has been fixed by MNG-6538.

• Issue related to missing event for ToolchainsBuildingResult on EventSpy MNG-6558.

• Issue related to support Java 9+ ClassLoader.findClass(String moduleName, String name) in Mojos. This has been fixed with MNG-6543.

• Improvement about the memory consumption has been done with MNG-6571.

• Issue related to relative parent POM resolution failing in 3.5.0 with complex multimodule builds has been fixed with MNG-6261.

• Missing export for org.slf4j.event.Level has been done with MNG-6618

User visible Changes

Maven has now a an option to suppress the transfer progress when downloading/uploading in interactive mode.

1

mvn --no-transfer-progress ....

or in short:

1

mvn -ntp ... ....

There had been an issues like MNG-6505 and MNG-6059 related to the construction of URL’s etc. within distributionManagement and scm part in the pom for multi module builds like this:

1
2
3
4
5
6

<scm child.scm.connection.inherit.append.path="true"
     child.scm.developerConnection.inherit.append.path="true"
     child.scm.url.inherit.append.path="true" />
<distributionManagement>
   <site child.site.url.inherit.append.path="true" />
 </distributionManagement>

Detailed explanations can be found in Inheritance Assembly and in MNG-6059

The detailed issue list

Bugs:

• MNG-5705 – NPE on parallel build in BuilderCommon.handleBuildError(BuilderCommon.java:147)
• MNG-5965 – Parallel build multiplies work if multiple goals are given
• MNG-5995 – Maven itself cannot run without maven-compat
• MNG-6256 – Maven script can break if “-f” path contains special characters
• MNG-6261 – Relative parent POM resolution failing in 3.5.0 with complex multimodule builds
• MNG-6262 – getCanonicalFile() is not used consistently during project resolution
• MNG-6346 – … was unexpected at this time when using -f option and path contains brackets
• MNG-6374 – ModelBuilder hangs with malformed pom.xml
• MNG-6429 – Integration Test site publishing requires Java 7 (or javadoc errors ignored)
• MNG-6495 – ModelResolver cannot be null
• MNG-6505 – child.(x.y).inherit.append.path value should be inherited
• MNG-6506 – Mojos are unable to load package annotations on Java >= 9
• MNG-6529 – ProjectBuilder.build(List<File> projects, boolean, ProjectBuildingRequest) doesn’t honor ProjectBuildingRequest.isResolveDependencies()
• MNG-6530 – Regression in ProjectBuilder when file change between invocations (introduced by MNG-6311)
• MNG-6533 – ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in exception report
• MNG-6543 – Upgrade plexus classworld to support java 9+ ClassLoader.findClass(String moduleName, String name) in Mojos
• MNG-6558 – ToolchainsBuildingResult event is not sent on EventSpy
• MNG-6577 – pom.xml: Uncaught IllegalArgumentException when parsing unicode entity ref
• MNG-6590 – DefaultProjectArtifactsCache java.lang.IllegalStateException: Duplicate artifact resolution result
• MNG-6599 – unknown version in model id when version is defined from parent

Improvements

• MNG-6059 – Important use cases not covered, as child.inherit.append.path affects all children
• MNG-6159 – Child path adjustments break git scm urls
• MNG-6213 – Maven doesn’t check the validity of scope value
• MNG-6481 – Allow to compile and test Maven with Java 11
• MNG-6513 – Replace depreated Plexus javadoc tags with annotations in ITs
• MNG-6515 – Fix javadoc build errors under Java 8 and 11
• MNG-6520 – Update assembly descriptors to 2.0.0
• MNG-6522 – Prepare Maven’s Core Integration Test Suite to test with Java 12 and 13-ea
• MNG-6572 – use int or long instead of BigIntegers for little numbers in ComparableVersion
• MNG-6593 – track input location for super-pom
• MNG-6597 – add input location tracking for plugins configuration
• MNG-6600 – add input location tracking for default lifecycle bindings executions
• MNG-6601 – add input location tracking for site’s reportPlugins injected by reports conversion
• MNG-6605 – Allow to suppress download messages in interactive mode
• MNG-6611 – Update animal-sniffer-maven-plugin to 1.17

Wish

• MNG-6571 – Maven memory consumption issue

Task

• MNG-6538 – Upgrade Maven Artifact Resolver to 1.3.3 to restore API
• MNG-6544 – Replace CacheUtils#{eq,hash} with Objects
• MNG-6573 – Use latest Maven 3.6.0 to build Maven Core and plugins with ASF CI
• MNG-6618 – Maven doesn’t export org.slf4j.event.Level

Dependency upgrade

• MNG-6526 – Upgrade to Wagon 3.3.1 (from 3.2.0)
• MNG-6591 – Upgrade to Wagon 3.3.2

The full list of changes can be found in our issue management system.

Complete Release Notes

See complete release notes for all versions

• The Apache Maven Team.

The Apache Maven team is pleased to announce the release of the Apache Maven SCM, version 1.11.2.

Maven SCM supports Maven 2.x plugins (e.g. maven-release-plugin) and other tools (e.g. Continuum) by providing them with a common API for doing SCM operations. You can look at the list of SCMs for more information on using Maven SCM with your favorite SCM tool.

You can download the appropriate sources etc. from the download page.

Release Notes – Maven SCM Version 1.11.2

Bug:

• SCM-777 – scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property

New Features:

• SCM-318 – Allow tags to be removed with Git implementation
• SCM-832 – maven-scm-provider-jgit should support SSH public key auth

Improvements:

• SCM-917 – Allow tags to be removed with Subversion implementation
• SCM-919 – Fix codecheck violations in JGit provider

Enjoy,

-The Apache Maven team

The Apache Maven team is pleased to announce the release of the Apache Maven Resolver, version 1.3.3

Apache Maven Artifact Resolver is a library for working with artifact repositories and dependency resolution.

Maven Artifact Resolver deals with the specification of local repository, remote repository, developer workspaces, artifact transports and artifact resolution.

It is expected to be extended by concrete repository implementation, like Maven Artifact Resolver Provider for Maven repositories or any other provider for other repository formats.

You can download the appropriate sources etc. from the download page.

Release Notes – Maven Resolver – Version Maven Artifact Resolver 1.3.3

Bug:

• MRESOLVER-67 – The Maven resolver API 1.3.2 JAR deployed on Maven central has been built with Java 11

Wish:

• MRESOLVER-53 – Document runtime exceptions

Enjoy,

• The Apache Maven team

The Apache Maven team is pleased to announce the release of the Maven Archiver, version 3.4.0.

The Maven Archiver is mainly used by plugins to handle packaging. The version numbers referenced in the Since column on this page are the version of the Maven Archiver component – not for any specific plugin. To see which version of Maven Archiver a plugin uses, go to the site for that plugin.

You should specify the version in your project’s dependency configuration:

1
2
3
4
5

<dependency>
  <groupId>org.apache.maven.shared</groupId>
  <artifactId>maven-archiver</artifactId>
  <version>3.4.0</version>
</plugin>

You can download the appropriate sources etc. from the download page.

Release Notes – Maven Archiver – Version 3.4.0

Bugs:

• MSHARED-588 – User supplied Class-Path entry does not go first
• MSHARED-782 – Deprecated option classpathMavenRepositoryLayout not marked as deprecated in the documentation
• MSHARED-783 – Archiver documentation issue tracker 404

New Features:

• MSHARED-787 – Add optional buildEnvironment information to the manifest
• MSHARED-798 – Add addDefaultEntries option (true by default)

Improvements:

• MSHARED-362 – Support removing default manifest entries with Maven Archiver
• MSHARED-777 – Remove deprecated main attributes from generated manifest
• MSHARED-799 – Change “Created-By” manifest entry value to be reproducible
• MSHARED-800 – Remove Maven version from pom.properties

Wishes:

• MSHARED-661 – Remove manifest entry “Built-By: ” for reproducible builds
• MSHARED-796 – use java.specification.version instead of java.version in Build-Jdk manifest entry

Task:

• MSHARED-797 – Move current Build-Jdk manifest entry to Build-Jdk-Spec

Dependency upgrade:

• MSHARED-781 – Upgrade to Plexus Archiver 4.1.0

Enjoy,

-The Apache Maven team