Apache Maven

Thursday April 07, 2022

Apache Maven Artifact Plugin Version 3.3.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Artifact Plugin, version 3.3.0.

The Artifact Plugin is used to manage artifacts tasks.

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-artifact-plugin</artifactId>
  <version>3.3.0</version>
</plugin>

Release Notes – Maven Artifact Plugin – Version 3.3.0

Release Notes – Maven Artifact Plugin – Version 3.3.0

  • Bug:

    • MARTIFACT-31 – wrong comparison results when buildinfo has been published to Central
  • New Feature:

    • MARTIFACT-24 – add artifact:check-buildplan goal to check that plugins versions do not have known reproducibility issues

Enjoy,

-The Apache Maven team

Tuesday April 05, 2022

Apache Maven Clean Plugin Version 3.2.0 Released

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

The Clean Plugin is used when you want to remove files generated at build-time in a project’s directory.

Important Note:

  • Maven 3.2.5+ only
  • JDK 8 minimum requirement

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

Release Notes – Maven Clean Plugin – Version 3.2.0

Release Notes – Maven Clean Plugin – Version 3.2.0

  • New Feature

    • MCLEAN-95 – Provide a fast deletion option
  • Improvements:

    • MCLEAN-89 – Add GitHub Information
    • MCLEAN-90 – Custom search broken on pages rendered using Fluido Skin 1.7
    • MCLEAN-91 – Upgrade maven-plugins to 34
    • MCLEAN-98 – Upgrade maven-plugin parent to 35
  • Tasks:

  • Dependency upgrades:

    • MCLEAN-87 – Upgrade maven-plugins parent to version 32
    • MCLEAN-92 – Require Maven 3.1.1 (drop dependency to Maven 3.0)
    • MCLEAN-96 – Require Maven 3.2.5+

Enjoy,

-The Apache Maven team

Monday April 04, 2022

Apache Maven Surefire/Failsafe Plugin Version 3.0.0-M6 Released

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

The release contains 111 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>3.0.0-M6</version>
</plugin>

or for failsafe:

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

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

Release Notes – Maven Surefire – Version 3.0.0-M6

  • Bugs:

    • SUREFIRE-1398 – TestNG test fails when both JUnitCore provider and TestNG provider are on classpath
    • SUREFIRE-1426 – Fork crash doesn’t fail build with -Dmaven.test.failure.ignore=true
    • SUREFIRE-1432 – trimStackTrace = false by default
    • SUREFIRE-1556 – Test XML file is not valid when rerun “fails” with an assumption
    • SUREFIRE-1659 – Log4j logger in TestExecutionListener corrupts Surefire’s STDOUT.
    • SUREFIRE-1800 – SurefireForkChannel binds to wrong IP
    • SUREFIRE-1806 – Site: Link to “TCP/IP Communication between Forks” is broken
    • SUREFIRE-1809 – Differences between Oracle JDK and AdoptOpenJDK caused by JPMS
    • SUREFIRE-1815 – Thread interrupted state cleared on any console output
    • SUREFIRE-1820 – Using SurefireForkNodeFactory with JDK8 results in NoSuchMethodError
    • SUREFIRE-1840 – Why sudo docker?
    • SUREFIRE-1842 – Surefire – NPE at end of successful test run
    • SUREFIRE-1844 – Trademarks / privacy policy footer displays broken
    • SUREFIRE-1851 – NPE in SmartStackTraceParser causes false positive test results
    • SUREFIRE-1857 – JUnit 5 report does not contain assertion failure message
    • SUREFIRE-1865 – ChecksumCalculator getSha1 does not compute checksums correctly
    • SUREFIRE-1869 – Classloader.getResource() doesn’t encode blanks with forkCount=0
    • SUREFIRE-1881 – Java agent printing to native console makes build block when using SurefireForkNodeFactory
    • SUREFIRE-1882 – Fix failures when compiled on Java 9+ and run on Java 8
    • SUREFIRE-1890 – Not compatible with TestNG 7.4.0
    • SUREFIRE-1894 – Surefire report XML schema is incomplete (attribute version not allowed in testsuite)
    • SUREFIRE-1909 – Support JUnit 5 reflection access by changing add-exports to add-opens
    • SUREFIRE-1910 – Missleading error message when using -Dtest=….
    • SUREFIRE-1912 – user.dir should not be set lazily within the surefire fork JVM
    • SUREFIRE-1913 – system properties should be restored after the in-process tests have been executed
    • SUREFIRE-1914 – XML report omits method signature / display name of Junit 5 parameterized tests if testset reporter is configured to use phrased naming
    • SUREFIRE-1926 – Console logs should be synchronized
    • SUREFIRE-1935 – Upgrade to JUnit Platform 1.8, start Launcher via LauncherSession
    • SUREFIRE-1945 – crashed tests – unit tests with large logging output does not produce surefire report
    • SUREFIRE-1967 – High resource consumption when executing TestNG tests in parallel mode with a suite file
    • SUREFIRE-1975 – JDK18 – The Security Manager is deprecated and will be removed in a future release
    • SUREFIRE-1982 – Fix failures (java.nio.ChartBuffer) when compiled on Java 9+ and run on Java 8
    • SUREFIRE-1983 – Corrupted STDOUT by directly writing to native stream in forked JVM 1. [setupJunitLogger() should be called AFTER startCapture()]
    • SUREFIRE-1990 – The previous XML report should be deleted before new run or re-run
    • SUREFIRE-1993 – Failsafe fails to detect module dependencies
    • SUREFIRE-2002 – TCP client throws WritePendingException
    • SUREFIRE-2006 – Don’t use Services Transformer in shadefire
    • SUREFIRE-2023 – The integration test Surefire946KillMainProcessInReusableForkIT hanged and timed out because SIGTERM happened before the first test has started. The plugin should be able to terminate itself whenever after SIGTERM.
    • SUREFIRE-2036 – Regression: 3.0.0-M5 fails with configured JUnit 5 provider
    • SUREFIRE-2040 – No tests executed with junit-platform-suite and -Dtest=TestSuite
  • New Features:

    • SUREFIRE-756 – Allow ability to capture executed random runOrder for re-play purposes
    • SUREFIRE-1854 – Support include/exclude junit test engine
    • SUREFIRE-1860 – extend ReportEntry interface and SimpleReportEntry with mandatory properties runMode:String, testRunId:long
    • SUREFIRE-1878 – Add failOnFlakeCount option
    • SUREFIRE-1893 – New maven-surefire JUnit5 extension by Fabricio Yamamoto
    • SUREFIRE-1964 – Method filtering support on excludes and includes file
  • Improvements:

    • SUREFIRE-1824 – failsafe-summary.xml should properly use UTF-8
    • SUREFIRE-1825 – Unable to zip the Cucumber TXT report file on Linux and MacOS
    • SUREFIRE-1826 – Improved performance of ThreadedStreamConsumer
    • SUREFIRE-1827 – The console output is not flushed
    • SUREFIRE-1845 – Fixed the performance of Utf8RecodingDeferredFileOutputStream as a bottleneck for the tests with logs
    • SUREFIRE-1846 – Remove Base64 in the Encoder/Decoder and gain the performance for the communication flow: Fork to Plugin
    • SUREFIRE-1847 – Remove Base64 in the Encoder/Decoder and gain the performance for the communication flow: Plugin to Fork
    • SUREFIRE-1853 – Clarify useModulePath documentation
    • SUREFIRE-1856 – Updated documentation for the TestNG Provider – may not disable JUnit in suiteXmlFiles
    • SUREFIRE-1858 – Change default debug options to not use legacy options
    • SUREFIRE-1954 – move inner class ProviderList to upper level
    • SUREFIRE-1955 – Switch project to Java 8
    • SUREFIRE-1957 – Get rid of maven-artifact-transfer
    • SUREFIRE-1958 – Replace fest-assert by AssertJ
    • SUREFIRE-1959 – Update plugin (requires Maven 3.2.5+)
    • SUREFIRE-1965 – Refactor beanshell script in project
    • SUREFIRE-1972 – Use current version of surefire-shared-utils
    • SUREFIRE-1987 – Refactor ProviderDetector#autoDetectOneWellKnownProvider
    • SUREFIRE-1992 – Increase output length of test errors/failures in summary
    • SUREFIRE-1994 – Upgrade and configure javacc-maven-plugin in module surefire-grouper
    • SUREFIRE-1995 – Ping and process checker should use isolated schedulers and the errors should be logged
    • SUREFIRE-1997 – InterruptedIOException and cause:InterruptedException have the same purpose and should be caught in CommandReader
    • SUREFIRE-1998 – Interrupted PPID Checker should have the same meaning as stopped PPID Checker
    • SUREFIRE-1999 – PPID checker should redirect the error stream of the checker command to a dump file
    • SUREFIRE-2005 – Improved dump message “Boot Manifest-JAR contains absolute paths in classpath” with exception message
    • SUREFIRE-2009 – Refactoring of surefire-junit3. JUnitTestSetExecutor and PojoTestSetExecutor should be stateless.
    • SUREFIRE-2011 – Updated abstractions which helps associating standard out/err with a test
    • SUREFIRE-2012 – Use maven-shared-utils instead of surefire-shared-utils in Report Parser. Removed commons-lang in Report Plugin.
    • SUREFIRE-2014 – Implement testRunId and RunMode in the EventEncoder and EventDecoder
    • SUREFIRE-2015 – Implement testRunId and RunMode in the SimpleReportEntry
    • SUREFIRE-2016 – The MOJO parameter testSourceDirectory is used only in the TestNG HTML, and it should be optional. Javadoc and documentation should be fixed.
    • SUREFIRE-2017 – Unstable build with ParallelParameterized
    • SUREFIRE-2019 – ThreadedStreamConsumer – use Thread.join() instead of CountDownLatch.await()
    • SUREFIRE-2020 – Use addShutDownHook() from maven-shared-utils
    • SUREFIRE-2021 – Commands should be flushed immediately. Use Channels.newChannel() instead of newBufferedChannel(). Delete the old flushing mechanism on forked processes.
    • SUREFIRE-2024 – Replace testng-junit5 by testng-engine in tests and documentation
    • SUREFIRE-2025 – Updated abstractions which helps associating systemProperties() with a test context
    • SUREFIRE-2026 – Improve assertions in Surefire1787JUnit5IT
    • SUREFIRE-2031 – Both fields/parameters “includes” and “excludes” should be in target MOJO class. User properties should be unique.
    • SUREFIRE-2042 – Remove unused method TestListResolver#getWildcard
    • SUREFIRE-2046 – Resolved TODOs. Updated callbacks ForkedProcessPropertyEventListener and ForkedProcessStandardOutErrEventListener.
    • SUREFIRE-2051 – Propagate ArtifactResolutionException while resolving artifacts in SurefireDependencyResolver
    • SUREFIRE-2052 – Handles internal exceptions do not have suppressed exceptions in ThreadedStreamConsumer
  • Test:

  • Wish:

    • SUREFIRE-1908 – Wish by Stackoverflow – Documented strategy with parallel Java packages
  • Tasks:

    • SUREFIRE-1807 – Shadefire should not duplicate entries in Provider SPI
    • SUREFIRE-1889 – Support Java 16 in Surefire Integration Tests
  • Dependency upgrades:

Enjoy,

-The Apache Maven team

Tuesday March 29, 2022

Apache Maven Shade Plugin, Version 3.3.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Shade Plugin, version 3.3.0.

This plugin provides the capability to package the artifact in an uber-jar, including its dependencies and to shade – i.e. rename – the packages of some of the dependencies.

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-shade-plugin</artifactId>
  <version>3.3.0</version>
</plugin>

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

Release Notes – Maven Shade Plugin – Version 3.3.0

  • Bugs:

    • MSHADE-252 – shadeSourcesContent is broken when combined with partial relocation
    • MSHADE-396 – Improve SourceContent Shading
  • New Feature:

    • MSHADE-36 – Add option to include dependency reduced POM instead of original one
  • Improvements:

    • MSHADE-321 – Always respect ‘createDependencyReducedPom’ flag
    • MSHADE-371 – Update Shade Apache[Notice/LICENSE]ResourceTransformer to use also [NOTICE/LICENSE].md
    • MSHADE-373 – Source transformation on source jar can break OSGi resolution due to duplicated bundle name
    • MSHADE-382 – Add an option to skip execution
    • MSHADE-391 – Do not modify class files, if nothing was relocated
    • MSHADE-405 – ShowOverlapping Uses http instead of https
  • Tasks:

    • MSHADE-389 – Get rid of old baggage
    • MSHADE-390 – Implement Sisu index transformer
    • MSHADE-401 – Improve ServiceResourceTransformer
    • MSHADE-412 – SimpleRelocator can fail in NPE, in particular with manifest transformer
  • Dependency upgrades:

    • MSHADE-379 – Support Java 16 – upgrade ASM to 9.0
    • MSHADE-386 – Update JDependency to 2.6.0
    • MSHADE-407 – Update ASM to 9.2 to support Java 17

Enjoy,

-The Apache Maven team

Thursday March 24, 2022

Apache Maven Shared Component: Maven Verifier Version 1.8.0 Released

The Apache Maven team is pleased to announce the release of the Maven Verifier, version 1.8.0.

This library provides a test harness for Maven integration tests.

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-verifier</artifactId>
    <version>1.8.0</version>
</dependency>

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

Release Notes – Maven Verifier – Version 1.8.0

  • Bug:

    • MSHARED-1015 – Using Embedded3xLauncher fails with “-Dmaven.multiModuleProjectDirectory system property is not set”
  • New Feature:

  • Improvements:

Enjoy,

-The Apache Maven team

Sunday March 20, 2022

Apache Maven JXR Plugin Version 3.2.0 Released

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

This module generates browsable HTML pages from Java source code.

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

NOTE: Special thanks for the contributions retrieved during the hackathon at JCreate.

Release Notes – Maven JXR – Version 3.2.0

  • Bug:

    • JXR-164 – Full path to local code sources in page title
  • Task:

    • JXR-162 – Lift Minimum Java to Java 8
  • Dependency upgrades:

    • JXR-157 – Upgrade Velocity templating engine
    • JXR-163 – Require Maven 3.2.5+
    • JXR-165 – Upgrade Maven Reporting to 3.1.0
    • JXR-167 – Upgrade Parent to 35
    • JXR-168 – Dependency upgrade and cleanup

Enjoy,

-The Apache Maven team

Sunday March 13, 2022

Apache Maven 3.8.5 Released

The Apache Maven team is pleased to announce the release of the Apache Maven 3.8.5

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.

Maven 3.8.5 is available via https://maven.apache.org/download.cgi

The core release is independent of plugin releases. Further releases of plugins will be made separately.

If you have any questions, please consult:

Release Notes – Maven – Version 3.8.5

  • Bugs:

    • MNG-5180 – Versioning’s snapshot version list is not included in metadata merge
    • MNG-5561 – Plugin relocation loses configuration
    • MNG-5982 – The POM for … is invalid, transitive dependencies … while property was overriden
    • MNG-6326 – Build continues when core extensions aren’t found
    • MNG-6727 – Using version range in parent and CI Friendly Version fails
    • MNG-6802 – FileProfileActivator changes FileProfileActivator.exists which lets flattened resolveCiFriendliesOnly depending fail activating profile
    • MNG-7156 – Parallel build can cause issues between clean and forked goals
    • MNG-7335 – [Regression] Parallel build fails due to missing JAR artifacts in compilePath
    • MNG-7347 – SessionScoped beans should be singletons for a given session
    • MNG-7357 – All Maven Core JARs have unusual entry order
    • MNG-7362 – DefaultArtifactResolver has spurious “Failure detected” INFO log
    • MNG-7374 – Mutating RelocatedArtifact does not retain type
    • MNG-7386 – ModelMerger$MergingList is not serializable
    • MNG-7402 – BuildListCalculator never detaches the classloader
    • MNG-7417 – Several classes do not set properties properly for building requests
  • New Features:

    • MNG-7395 – Support interpolation in extensions.xml
    • MNG-7407 – Introduce a ModelVersionProcessor component to make CI Friendly Versions pluggable
  • Improvements:

    • MNG-6960 – Use RuntimeInformation instead of reading properties
    • MNG-7349 – Limit relocation warning message to direct dependencies only
    • MNG-7380 – Don’t log non-threadsafe warning if only building a single module
    • MNG-7381 – Shorten parallel builder thread name to artifactId, conditionally with groupId
    • MNG-7385 – Improve documentation on repository metadata
    • MNG-7400 – Allow more WorkspaceReaders to participate
    • MNG-7408 – Explain reporting plugin version automatic selection (in Maven 3)
  • Dependency upgrades:

    • MNG-7370 – Upgrade Maven Wagon to 3.5.1
    • MNG-7384 – Upgrade Maven JAR Plugin to 3.2.2
    • MNG-7428 – Upgrade Maven Parent to 35

For more information read https://maven.apache.org/docs/3.8.5/release-notes.html

Enjoy!

  • The Maven Team

Friday March 11, 2022

Apache Maven Dependency Plugin Version 3.3.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Dependecy Plugin, version 3.3.0.

The dependency plugin provides the capability to manipulate artifacts. It can copy and/or unpack artifacts from local or remote repositories to a specified location.

https://maven.apache.org/plugins/maven-dependency-plugin/

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-dependency-plugin</artifactId>
    <version>3.3.0</version>
</plugin>

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

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

Release Notes – Maven Dependency Plugin – Version 3.3.0

  • Bugs:

    • MDEP-679 – mvn dependency:analyze detected wrong transitive dependency
    • MDEP-742 – dependency plugin does not work with JDK 16
    • MDEP-752 – skip dependency analyze in ear packaging
    • MDEP-753 – Non-test dependency reported as Non-test scoped test only dependency
    • MDEP-759 – ‘Dependency not found’ with 3.2.0 and Java-17 while analyzing
    • MDEP-761 – Tree plugin does not terminate with 3.2.0
    • MDEP-769 – Minor improvement – continue
    • MDEP-774 – analyze-only failed: PermittedSubclasses requires ASM9
    • MDEP-781 – Broken Link to “Introduction to Dependency Mechanism Page”
    • MDEP-783 – TreeMojo docs say scope doesn’t work due to MSHARED-4
    • MDEP-786 – Sealed classes not supported
  • New Feature:

    • MDEP-787 – Allow ignoring non-test-scoped dependencies
  • Improvements:

    • MDEP-763 – Minor improvements
    • MDEP-768 – GitHub Action build improvement
    • MDEP-779 – dependency:analyze should list the classes that cause a used undeclared dependency
    • MDEP-789 – Improve documentation of analyze – Non-test scoped
  • Task:

  • Dependency upgrades:

    • MDEP-766 – Upgrade maven-invoker-plugin to version 3.2.2
    • MDEP-784 – Upgrade maven-dependency-analyzer to 1.12.0
    • MDEP-788 – Upgrade maven-reporting-impl to version 3.1.0
    • MDEP-795 – Update Jetty to 9.4.45.v20220203
    • MDEP-796 – Upgrade Maven Parent to 35
    • MDEP-797 – Update transitive dependency commons-beanutils to 1.9.4
    • MDEP-798 – Upgrade maven-dependency-tree from 3.0.1 to 3.1.0

Enjoy,

-The Apache Maven team

Apache Maven Compiler Plugin Version 3.10.1 Released

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

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

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

Release Notes – Maven Compiler Plugin – Version 3.10.1

  • Bugs:

    • MCOMPILER-346 – workaround to jdk bug: assertionError inside javac when using javax.tools API
    • MCOMPILER-485 – Incorrect internal string format in generated package-info.class files on Windows
  • New Feature:

    • MCOMPILER-426 – dedicated option for enabling preview feature

Enjoy,

  • The Apache Maven team

Thursday March 03, 2022

Apache Maven Parent POM's Version 35 Released

The Apache Maven team is pleased to announce the release of the Maven Parent POMs Version 34

Maven Parent POMs include Maven Parent POM itself, but also Maven Plugins Parent POM, Maven Shared Components Parent POM, Maven Skins Parent POM and Maven Doxia Tools Parent POM.

https://maven.apache.org/pom/maven/

You should specify the version in your project as parent like the following:

1
2
3
4
5
<parent>
   <groupId>org.apache.maven</groupId>
   <artifactId>maven-parent</artifactId>
   <version>35</version>
</parent>

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

https://maven.apache.org/pom/maven/download.html

Release Notes – Apache Maven Parent POM – Version 34

  • Bugs:

    • MPOM-242 – fix mono-module site easy-deployment
    • MPOM-243 – WARNING: release:perform issues [WARNING] The requested profile “pom.xml” could not be activated because it does not exist.
    • MPOM-253 – issue management URL incorrect
  • New Feature:

    • MPOM-274 – use Shared GitHub Actions
  • Improvements:

    • MPOM-268 – Removed unused property
    • MPOM-276 – streamLogsOnFailures for maven-invoker-plugin as default
    • MPOM-278 – add “Extensions” entry to “Maven Projects” menu
    • MPOM-279 – Get rid of findbugs-maven-plugin
    • MPOM-280 – Remove detectLinks from maven-javadoc-plugin
    • MPOM-298 – Cleanup dependencyLocationsEnabled from MPIR configuration
  • Tasks:

    • MPOM-270 – Fix enforcer use
    • MPOM-271 – Create helper profile to “ban legacy”
    • MPOM-272 – Remove legacy from doxia parent depMgmg
    • MPOM-273 – Update maven-plugin-plugin to 3.6.2
    • MPOM-281 – Update maven-plugin-plugin to 3.6.4
  • Dependency upgrades:

    • MPOM-239 – upgrade plexus-component-metadata to 2.1.0 for better Reproducible Build
    • MPOM-250 – remove the JavaDoc taglets from maven-parent (both to extract Mojo javadoc annotations and link in javadoc)
    • MPOM-292 – upgrade parent to ASF 25

Enjoy, – The Apache Maven Team

Friday February 25, 2022

Maven Project Info Reports Plugin version 3.2.2 Released

The Apache Maven team is pleased to announce the release of the Maven Project Info Reports Plugin version 3.2.2

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-project-info-reports-plugin</artifactId>
  <version>3.2.2</version>
</plugin>

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

Release Notes – Maven Project Info Reports Plugin – Version 3.2.2

  • Bug:

    • MPIR-413 – Plugin repositories defined in project are not used by plugin-management report
  • Dependency upgrade:

    • MPIR-414 – Upgrade Maven Reporting API/Impl to 3.1.0

Enjoy,

-The Apache Maven team

Sunday February 20, 2022

Apache Maven Doxia Sitetools 2.0.0-M2 Released

The Apache Maven team is pleased to announce the release of the Doxia Site Tools Version 2.0.0-M2, 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.

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

https://maven.apache.org/doxia/doxia-sitetools/download.cgi

Release Notes – Maven Doxia base – Version 2.0.0-M2

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

Release Notes – Maven Doxia Sitetools – Version 2.0.0-M2

Enjoy,

-The Apache Maven team

Thursday February 17, 2022

Apache Maven Indexer Version 6.1.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Indexer, version 6.1.1.

Apache Maven Indexer (former Sonatype Nexus Indexer) is the de facto standard for producing indexes of Maven repositories. The Indexes are produced and consumed by all major tools in the ecosystem.

Most notable changes: * Java 8 required * Lucene upgraded to latest 8.x (8.11.1) * Guava and TrueZip dependencies removed

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

https://maven.apache.org/maven-indexer/download.cgi

Release Notes – Maven Indexer – Version 6.1.1

  • Bugs:

    • MINDEXER-123 – Fix an InputStream leak in indexer-reader Utils
    • MINDEXER-127 – Maven repository indexing error: java.nio.channels.OverlappingFileLockException
    • MINDEXER-133 – Reset the correct stream in IndexDataReader
    • MINDEXER-135 – Fix CLI shading
    • MINDEXER-138 – Indexer Core Jetty test dependency is not in test scope
  • Improvements:

    • MINDEXER-104 – Migrate the indexer to Lucene 8.x
    • MINDEXER-110 – Upgrade parent to 31
    • MINDEXER-114 – Extend JarFileContentsIndexCreator to support zip files
    • MINDEXER-115 – Remove deprecated usages of BooleanQuery constructor – use Builder instead
    • MINDEXER-116 – Move to Java 8 as minimum Java version
    • MINDEXER-117 – Add ability to set the temporary index directory for index update
    • MINDEXER-118 – Remove usages of pre-Lucene 4.0 deprecated code
    • MINDEXER-120 – Remove TrueZip dependency
    • MINDEXER-122 – Add getName() to Record.EntryKey
    • MINDEXER-129 – Shared GitHub Actions
    • MINDEXER-132 – use Files.createTempDirectory(…) instead of custom code around File.createTempFile(…)
  • Tasks:

    • MINDEXER-109 – switch from Git-WIP to Gitbox
    • MINDEXER-113 – Excluding additional dependencies from shaded jar
    • MINDEXER-134 – Update dependencies (except Lucene)
    • MINDEXER-137 – Align example packages with indexer packages
    • MINDEXER-139 – Decouple from Plexus APIs
    • MINDEXER-140 – DefaultIndexingContext double invocation of setIndexDirectoryFile method
  • Dependency upgrades:

Enjoy,

-The Apache Maven team

Wednesday February 16, 2022

Apache Maven Site Plugin Version 3.11.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Site Plugin, version 3.11.0.

The Site Plugin is used to generate a site for the project. The generated site also includes the project’s reports that were configured in the POM.

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

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

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-site-plugin</artifactId>
  <version>3.11.0</version>
</plugin>

Release Notes – Maven Site Plugin – Version 3.11.0

  • Task:

    • MSITE-880 – AbstractSiteDeployWebDavTest should not log
  • Dependency upgrades:

    • MSITE-881 – Upgrade Maven Reporting API to 3.1.0
    • MSITE-882 – Upgrade Maven Reporting Exec to 1.6.0
    • MSITE-883 – Upgrade plugins in ITs

Enjoy,

-The Apache Maven team

Tuesday February 15, 2022

Apache Maven PMD Plugin Version 3.16.0 Released

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

Release Notes – Apache Maven PMD Plugin – Version 3.16.0

  • Bugs:

    • MPMD-325 – Could not find class due to IncompatibleClassChangeError warning
    • MPMD-324 – Ruleset URLs have hyphen replaced with forwardslash
    • MPMD-323 – ResourceManager should use project base dir instead of pom location
  • Improvement:

  • Tasks:

    • MPMD-327 – Upgrade to PMD 6.42.0
    • MPMD-326 – Set Maven 3.1.1 as minimum version

Enjoy,

-The Maven team

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation