Apache Maven

Sunday May 19, 2019

Apache Maven Source Plugin Version 3.1.0 Released

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:

Improvement:

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

Dependency upgrades:

Enjoy,

-The Apache Maven team

Karl Heinz Marbaise

Monday May 13, 2019

Apache Maven JAR Plugin Version 3.1.2 Released

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

Monday May 06, 2019

Apache Maven Surefire Plugin Version 2.22.2 Released

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

Thursday May 02, 2019

Apache Maven Compiler Plugin, version 3.8.1

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

Wednesday May 01, 2019

Apache Maven Archetype Plugin, version 3.1.0

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:

Dependency upgrades:

Enjoy,

-The Apache Maven team

Tuesday April 23, 2019

Apache Maven PMD Plugin Version 3.12.0 Released

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:

Enjoy,

-The Maven team

Apache Maven Help Plugin Version 3.2.0 Released

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

Saturday April 13, 2019

Apache Maven Release 3.6.1

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:

Code Contributors of this release:

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-6529ProjectBuilder.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-6533ProjectBuilder.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.

Thursday March 21, 2019

Apache Maven SCM Version 1.11.2 Released

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

Friday March 15, 2019

Apache Maven Resolver Version 1.3.3 Released

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:

Note: The previous version 1.3.2 was accidently released based on JDK9+ usage which causes some usage issues which had been fixed with the Version 1.3.3.

Enjoy,

  • The Apache Maven team

Monday February 25, 2019

Apache Maven Shared Component: Maven Archiver Version 3.4.0 Released

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:

Enjoy,

-The Apache Maven team

Saturday February 09, 2019

Apache Maven Wagon 3.3.2 Released

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

Apache Maven Wagon is a transport abstraction that is used in Mavens artifact and repository handling code.

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

Release Notes – Maven Wagon – Version 3.3.2

Bugs:

  • WAGON-545 – Connection reset while downloading artifacts in cloud environment (Azure)
  • WAGON-546 – HttpWagon TTL not set
  • WAGON-554 – Tests with checkin rely on global Git config

Tasks:

  • WAGON-552 – Replace Commons Codec with Plexus Utils
  • WAGON-555 – Use java.nio.file.Path for URI construction of file:// URIs in tests
  • WAGON-556 – Skip parsing of user info for file:// URLs

Dependency upgrades:

Enjoy,

  • The Apache Maven team

Monday January 21, 2019

Apache Maven Invoker Plugin Version 3.2.0 Released

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

The Invoker Plugin is used to run a set of Maven projects. The plugin can determine whether each project execution is successful, and optionally can verify the output generated from a given project execution.

This plugin is in particular handy to perform integration tests for other Maven plugins. The Invoker Plugin can be employed to run a set of test projects that have been designed to assert certain features of the plugin under test.

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-invoker-plugin</artifactId>
  <version>3.2.0</version>
</plugin>

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

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

Release Notes – Maven Invoker Plugin – Version 3.2.0

Bug:

  • MINVOKER-243 – invoker:install doesn’t copy transitive dependencies anymore (as of 3.1.0)

Improvements:

Dependency upgrade:

  • MINVOKER-239 – Upgrade maven-plugins parent to version 32

Enjoy,

-The Apache Maven team

Sunday January 06, 2019

Apache Maven Wagon 3.3.1 Released

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

Apache Maven Wagon is a transport abstraction that is used in Mavens artifact and repository handling code.

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

Release Notes – Maven Wagon – Version 3.3.1

Bugs:

  • WAGON-538 – Basic authentication fails if the password contains non-ASCII characters
  • WAGON-543 – wagon-ssh download hangs

Improvements:

  • WAGON-537 – Maven transfer speed of large artifacts is slow due to unsuitable buffer strategy
  • WAGON-539 – Explicitly register only supported auth schemes
  • WAGON-540 – Switch to modern-day encoding (UTF-8) of auth credentials

Task:

Enjoy,

  • The Apache Maven team

Wednesday January 02, 2019

Apache Maven Assembly Plugin Version 3.1.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 3.1.1.

The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive.

Note:

  • Maven 3.X only
  • JDK 7 miminum requirement.

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-assembly-plugin</artifactId>
  <version>3.1.1</version>
</plugin>

Release Notes – Maven Assembly Plugin – Version 3.1.1

Bugs:

  • MASSEMBLY-675 – Maven Assembly packaging wildcard-excluded dependencies
  • MASSEMBLY-762 – Assembly plugin doesn’t exclude transitive dependencies when excluded by wildcards in dependencies section
  • MASSEMBLY-799 – Exclusion on wildcard, then the assembly would still package to include the excluded libraries
  • MASSEMBLY-861 – exclusion * also packaged
  • MASSEMBLY-873 – Maven-Assembly-Plugin freezes when building jar-with-dependencies of project depending on org.bouncycastle:bcprov-jdk15on:1.58
  • MASSEMBLY-893 – Typo in FAQ

Tasks:

  • MASSEMBLY-885 – remove unused unpack code
  • MASSEMBLY-898 – upgrade to plexus-io 3.1.1
  • MASSEMBLY-899 – Make deprecated and non used of parameter useJvmChmod parameter (plugin is now 1.7)
  • MASSEMBLY-901 – Fix trivial javadocs HTML errors
  • MASSEMBLY-902 – Some Integration tests fails if launched with an very large UID

Dependency upgrades:

Enjoy,

-The Apache Maven team

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation