Apache Maven

Thursday March 29, 2018

Apache Maven Shared Component: Maven Dependency Analyzer Version 1.9 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Dependency Analyzer Version 1.9

Analyzes the dependencies of a project for undeclared or unused artifacts.

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

1
2
3
4
5
<dependency>
  <groupId>org.apache.maven.shared</groupId>
  <artifactId>maven-dependency-analyzer</artifactId>
  <version>1.9</version>
</dependency>

Release Notes – Maven Dependency Analzyer Version 1.9

Bug:

  • MSHARED-710 – JDK 9 / 10 Issue – Unknown constant pool type

Dependency upgrades:

Enjoy,

-The Apache Maven team

Wednesday March 28, 2018

Apache Maven Help Plugin Version 3.0.1 Released

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

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.0.1</version>
</plugin>

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

Release Notes – Maven Help Plugin – Version 3.0.1

Bugs:

  • MPH-135 – help:effective-pom crashes with NPE in multi module builds with -Doutput set
  • MPH-139 – Invalid default namespace set for effective settings
  • MPH-140 – Multiple XML declarations written

Tasks:

  • MPH-137 – Use JDOM’s PrettyFormatter throughout
  • MPH-138 – Drop AbstractEffectiveMojo#addMavenNamespace()
  • MPH-141 – Use non-deprecated field in DateFormatUtils

Dependency upgrade:

  • MPH-136 – Upgrade JDOM to 1.1.3

Enjoy,

-The Apache Maven team

Sunday March 18, 2018

Maven Help Plugin Version 3.0.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Help Plugin, version 3.0.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.0.0</version>
</plugin>

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

Release Notes – Maven Help Plugin – Version 3.0.0

Bugs:

  • MPH-53 – mvn help:describe returns the version that is specified in metadata instead of the one in the parent pom
  • MPH-87 – help:effective-pom/effective-settings uses platform encoding and garbles non-ASCII characters, emits invalid XML
  • MPH-97 – [Patch] maven-help-plugin does not build with latest version of maven-plugin-testing-harness
  • MPH-99 – Evaluate has no output in quiet mode
  • MPH-105 – Effective pom aggregation is not triggered
  • MPH-107 – Mojos use inconsistent line endings throughout
  • MPH-108 – Patch for MPH-72 not fully applied
  • MPH-110 – Cannot run ITs successfully
  • MPH-111 – IT ‘effective-pom_properties’ fails if run with -Dinvoker.mergeUserSettings
  • MPH-114 – Goal fails with “Unable to get the POM for the artifact”
  • MPH-119 – The “artifact” parameter is not taken into account with Maven 3
  • MPH-121 – incorrect text in help:describe for cmd
  • MPH-123 – all-profiles does not show right active status

Improvements:

  • MPH-106 – add gav parameter to calculate effective pom for any gav, not only reactor
  • MPH-109 – Use ISO 8601 date format for the remaining goals
  • MPH-116 – Printout the information if a goal is a report goal or not
  • MPH-120 – Migrate plugin to Maven 3.0
  • MPH-124 – Show parameter aliases in describe goal

Tasks:

  • MPH-103 – Remove unused dependency maven-monitor
  • MPH-112 – Upgrade to Commons Lang3
  • MPH-126 – Require Java 7
  • MPH-132 – Drop parameter ‘medium’
  • MPH-133 – Drop deprecated alias ‘full’
  • MPH-134 – Drop deprecated alias ‘mojo’

Dependency upgrades:

  • MPH-102 – Upgrade to maven-plugins parent version 27
  • MPH-104 – Upgrade maven-plugin-testing-harness to 1.3
  • MPH-117 – Upgrade plexus-utils to 3.0.22
  • MPH-118 – Upgrade maven-plugins to version 30
  • MPH-125 – Upgrade parent to 31
  • MPH-127 – Upgrade Maven Artifact Transfer to 0.9.1
  • MPH-128 – Upgrade Maven Reporting Exec to 1.4
  • MPH-129 – Upgrade Plexus Utils to 3.1.0
  • MPH-130 – Upgrade XStream to 1.4.7
  • MPH-131 – Ugprade Commons Lang to 3.7

Enjoy,

-The Apache Maven team

Monday March 12, 2018

Apache Maven EAR Plugin 3.0.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven EAR Plugin, version 3.0.0

This plugin generates Java EE Enterprise Archive (EAR) file. It can also generate the deployment descriptor file (e.g. application.xml).

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-ear-plugin</artifactId>
  <version>3.0.0</version>
</plugin>

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

Release Notes – Maven EAR Plugin – Version 3.0.0

Bugs:

  • MEAR-171 – Full customization of FileNameMapping is needed
  • MEAR-217 – Snapshot dependencies are not deleted from skinny WARs
  • MEAR-243 – Skinny WARs – JAR not removed from WAR if scope in EAR is set to provided
  • MEAR-244 – Remove link to non-existing Codehaus wiki
  • MEAR-246 – Upgrade the EAR lifecycle to use the maven-resources-plugin 3.0.2.
  • MEAR-250 – IT skinny-wars-javaee5 fails while running with JDK 9

New Features:

  • MEAR-247 – resource-ref in generated application.xml
  • MEAR-248 – Support lookup-name in env-entry section

Improvements:

  • MEAR-198 – Add LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin
  • MEAR-223 – Link to wiki on documentation page is pointing to shutdown codehaus
  • MEAR-226 – bundleFileName functionality for the acr plugin
  • MEAR-228 – Remove manifestFile parameter
  • MEAR-229 – Change default value for version parameter
  • MEAR-232 – Remove param properties that doesn’t make sense for CLI usage
  • MEAR-234 – Upgrade maven-shared-components parent to version 30
  • MEAR-241 – Change package to o.a.m.plugins
  • MEAR-242 – Update lifecycle mapping plugin version
  • MEAR-254 – Support JavaEE version 8
  • MEAR-258 – Upgrade site skin to 1.7
  • MEAR-260 – Remove finalName as a parameter
  • MEAR-261 – In cases where fileNameMapping is used fail the build
  • MEAR-262 – Missing since for outputFileNameMapping parameter
  • MEAR-263 – Wrong docs in examples/customize-file-name-mapping.html

Tasks:

  • MEAR-207 – Remove the JavaModule/Ejb3Module which are marked deprecated
  • MEAR-208 – Upgrade to Maven 3.0 compatiblity + JDK 6
  • MEAR-209 – Change and use a internal unique id instead of artifactId only
  • MEAR-259 – Fix formatting date issues in apt files

Dependency upgrades:

  • MEAR-224 – Upgrade plexus-archiver from 2.10.3 to 3.0.1
  • MEAR-233 – Upgrade plexus-archiver from 3.0.3 to 3.1.1
  • MEAR-235 – Upgrade maven-archiver to 3.1.0
  • MEAR-236 – Upgrade maven-filtering to 3.1.1
  • MEAR-237 – Upgrade plexus-archiver to 3.3
  • MEAR-238 – Upgrade of plexus-archiver to 3.4.
  • MEAR-240 – Upgrade of maven-archiver to 3.1.1.
  • MEAR-245 – Upgrade of plexus-interpolation to 1.24.
  • MEAR-251 – Upgrade maven-archiver to 3.2.0
  • MEAR-252 – Upgrade plexus-archiver to 3.5.
  • MEAR-253 – Upgrade plexus-utils to version 3.1.0
  • MEAR-255 – Upgrade parent to 31
  • MEAR-256 – Upgrade maven-verifier component
  • MEAR-257 – Upgrade JUnit to 4.12

Enjoy,

-The Apache Maven team

Thursday March 08, 2018

Apache Maven Version 3.5.3 Released

Release Notes – Maven 3.5.3

The Apache Maven team would like to announce the release of Maven 3.5.3

Maven 3.5.3 is available for download.

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 place.

The core release is independent of the plugins available. Further releases of plugins will be made separately. See the PluginList for more information.

We hope you enjoy using Maven! If you have any questions, please consult:

  • the web site: https://maven.apache.org/
  • the maven-user mailing list: https://maven.apache.org/mail-lists.html
  • the reference documentation: https://maven.apache.org/ref/3.5.3/

Reporters and Contributors of this release

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.

Bugs:

Improvements:

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

Preliminary Testers

Thank you also for your time and feedback.

Known Issues

One new issue was identified during the release testing. This issue affects Windows users. When running Maven with parallel threads, i.e. the -T command line option, Maven may output spurious ANSI escapes such as [0m [0m MNG-6372

Overview about the changes

  • Issues have been fixed related to colorizations like to clean up the situation while interrupting the build process MNG-6188 and some issues related to Git Bash / Cygwin have been fixed MNG-6282 and the new options -Dstyle.color MNG-6296 has been fixed.

  • The handling CRLF in jvm.config file has been fixed MNG-6255.

  • The wrong usage of the CI friendly version was not correctly identified which has been improved MNG-6305.

  • Wrong encoding of non-ascii filenames has been fixed MNG-6320.

  • Deadlock in dependency resolution has been fixed MNG-6323.

  • A regression related to parents relativePath verification has been fixed MNG-6330.

So now some more interesting things about new (small) features:

  • The log output contains now some progress informations related to the number of modules which looks like this MNG-6302:
[INFO] Building parent 5.0.1-SNAPSHOT                                     [1/9]

The number 1 is the current number which is being built where the 9 in this case is the number of modules which have to be built overall. So we are in module 1 of 9.

Furthermore the information about the packaging type and the groupId/artifactId are now being shown during the build like the following MNG-6308:

[INFO] ------------------< com.soebes.examples.j2ee:parent >-------------------
[INFO] Building parent 5.0.1-SNAPSHOT                                     [1/9]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]

And finally we have added the version of the modules or the reactor at the end of the build MNG-6352:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] parent 5.0.1-SNAPSHOT .............................. SUCCESS [  0.238 s]
[INFO] domain ............................................. SUCCESS [  0.014 s]
[INFO] service-client ..................................... SUCCESS [  0.008 s]
[INFO] webgui ............................................. SUCCESS [  0.010 s]
[INFO] service ............................................ SUCCESS [  0.007 s]
[INFO] app ................................................ SUCCESS [  0.005 s]
[INFO] appasm ............................................. SUCCESS [  0.005 s]
[INFO] shade .............................................. SUCCESS [  0.006 s]
[INFO] assembly 5.0.1-SNAPSHOT ............................ SUCCESS [  0.005 s]
[INFO] ------------------------------------------------------------------------

This can be helpful if you have a large number of modules to get the information about the version being built. This meant in the past to scroll up to the last module and look there for the version. Now this can simply being seen at the end of build. If you have a multi module build where the number is the same for all modules it will be given only on the first line and the last line. If you have an aggregator build the version will be printed out for each project.

  • One more thing has been optimized. We have removed the System.gc() call at the end of the build because this can cause costs for example on AWS systems related to the time taken to run Garbage Collection which is not really necessary MNG-6340. This means also the resulting output will change a little bit like this:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.111 s
[INFO] Finished at: 2018-02-25T15:34:10+01:00
[INFO] ------------------------------------------------------------------------

So there is no line anymore telling you about memory stuff.

  • If you have used the deprecated version markers like RELEASE or LATEST this will now produce a WARNING during the build MNG-6342.

The detailed issue list

Bugs:

  • MNG-6188 - Console color not properly reset when interrupting build process
  • MNG-6255 - Maven script cannot parse jvm.config with CRLF
  • MNG-6282 - Console output has no colors in shell (both Git Bash and Cygwin) (regression in Jansi 1.16 / Maven 3.5.1)
  • MNG-6296 - New option -Dstyle.color is not working
  • MNG-6298 - 3.5.2: ClassNotFoundException: javax.annotation.security.RolesAllowed
  • MNG-6300 - Multi module release creates empty directories in war file instead of jars
  • MNG-6305 - Validation of CI friendly version incorrect
  • MNG-6320 - Apparently wrong encoding of non-ascii java class filename in error messages in the maven log
  • MNG-6323 - Deadlock in multithreaded dependency resolution
  • MNG-6330 - (regression) Parents relativePath not verified anymore

New Feature

  • MNG-6302 - Provide some “progress” hints

Improvements

  • MNG-5992 - Git passwords are exposed as the Super POM still uses Maven Release Plugin 2.3.2
  • MNG-6306 - Replace use of Guava in maven-resolver-provider with a lighter weight alternative
  • MNG-6308 - display packaging & groupId:artifactId when building a module
  • MNG-6332 - Cleaned up mvn.cmd Script
  • MNG-6340 - (Performance) To make System.gc() call configurable in target summary code
  • MNG-6342 - Emit a WARNING about LATEST/RELEASE in parent
  • MNG-6352 - Printout version information at the end of the build

Task

  • MNG-6331 - Remove maven-bundle-pugin from build pluginManagement

Dependency upgrade

  • MNG-6312 - Update Maven Wagon dependency
  • MNG-6335 - Update test framework Mockito from 1.10 to 2.12
  • MNG-6353 - Upgrade maven-shared-utils to 3.2.1

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

Complete Release Notes

See complete release notes for all versions


Tuesday March 06, 2018

Apache Maven Surefire Plugin Version 2.21.0 Released

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

The release contains 33 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.21.0</version>
</plugin>

or for failsafe:

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-failsafe-plugin</artifactId>
  <version>2.21.0</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.21.0</version>
</plugin>

Release Notes – Maven Surefire – Version 2.21.0

Bugs:

  • SUREFIRE-1372 – Rerunning failing tests fails in combination with Description#createSuiteDescription
  • SUREFIRE-1422 – Forking fails on Linux if /bin/ps isn’t available
  • SUREFIRE-1424 – javax.transaction.TransactionManager not visible with Java9
  • SUREFIRE-1439 – NullPointerException on JDK10
  • SUREFIRE-1443 – surefire report: broken links with inner classes
  • SUREFIRE-1445 – Properties from configuration POM are not passed to Provider on JDK 9
  • SUREFIRE-1450 – TestNG Listener aren’t working from Property Tag in POM.xml With JDK9
  • SUREFIRE-1451 – Surefire Booter compatibility with NetBSD ps(1) output
  • SUREFIRE-1452 – Support filtering of tests from Base Class (TestNG)
  • SUREFIRE-1475 – PpidChecker.windows() assumes wmic is on the path

Improvements:

  • SUREFIRE-1183 – Custom Test Report Titles and Descriptions
  • SUREFIRE-1262 – Add modulepath support
  • SUREFIRE-1416 – maven-surefire-parser: add new method isError in ReportTestCase
  • SUREFIRE-1435 – Improve Thread Dump. Use prefix “surefire-forkedjvm” in daemon Threads in forked JVM
  • SUREFIRE-1448 – Clarified specifying multiple categories for JUnit
  • SUREFIRE-1453 – Allow to specify non existant classes as “groups”
  • SUREFIRE-1454 – Speedup Standard Output if Tests
  • SUREFIRE-1491 – LocationManager injected in MOJO unables plugin to run in JDK 1.6

Test:

  • SUREFIRE-1437 – Improve unit tests. Call PID parser on all platforms in SystemUtilsTest.

Wish:

Tasks:

  • SUREFIRE-1455 – JaCoCo on integration tests
  • SUREFIRE-1461 – UnicodeTestNamesIT should be able to run multiple times
  • SUREFIRE-1463 – integration tests should run on the top of JDK 9
  • SUREFIRE-1471 – Too long Windows path cause CI issues. Renamed surefire-intergation-tests to surefire-its.
  • SUREFIRE-1472 – Multibranch Pipeline supports JDK 7-10 Maven 3.2-3.5 Linux Windows
  • SUREFIRE-1481 – Surefire1295AttributeJvmCrashesToTestsIT should be Parameterized test instead of using Theories runner
  • SUREFIRE-1482 – Obsolete workaround with commons-lang3 in project unit tests
  • SUREFIRE-1484 – maven-clean-plugin should be used in integration test resource junit-pathWithUmlaut
  • SUREFIRE-1485 – surefire-shadefire project should not be deployed in Maven Central
  • SUREFIRE-1486 – maven-failsafe-plugin does not use JUnit adapter for JUnit4 annotations and TestNG providers do not have maven-surefire-plugin config in POM
  • SUREFIRE-1488 – Native library in Surefire1295AttributeJvmCrashesToTestsIT caused unstable test
  • SUREFIRE-1489 – Implement different HTTP ports in ITs and zip() in jenkinsfile

Dependency upgrade:

SUREFIRE-1434 – Upgrade PowerMock@Java9 to Version 2.0.0-beta.5

Enjoy,

-The Apache Maven team

Thursday March 01, 2018

Apache Maven JDeps Plugin, version 3.1.1

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

The JDeps Plugin uses the jdeps tool to analyze classes for internal API calls. For more information about the standard jdeps tool, please refer to https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool

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

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

Release Notes Maven JDeps Plugin Release Notes Version 3.1.1

Bugs:

  • MJDEPS-10 – Error: unknown option: -M while using module option of maven-jdeps-plugin

New Features:

  • MJDEPS-9 – Introduce failOnWarning as a named property
  • MJDEPS-11 – Introduce —multi-release option

Improvement:

  • MJDEPS-12 – Add support for the ‘-package’ options

Dependency upgrade:

  • MJDEPS-8 – Upgrade plexus-utils to version 3.1.0
  • MJDEPS-13 – Upgrade parent to 31

Enjoy,

-The Apache Maven team

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation