Apache Maven 4.0.0-beta-3 released
Tamás Cservenák <[email protected]> Sun, 26 May 2024 17:02:46 +0200
| Newsgroups | gmane.comp.apache.cxf.devel,gmane.comp.apache.maven.announce,gmane.comp.jakarta.avalon.user |
|---|---|
| Message-ID | <CAPLpRQKT3EnNkPF9DvOH_aeNJb7kCYnq6GMTbukyrnsuU+VJog__49160.3489661188$1716735808$gmane$org@mail.gmail.com> |
--0000000000004f4e8006195cb2c4
Content-Type: text/plain; charset="UTF-8"
The Apache Maven team is pleased to announce the release of the
Apache Maven 4.0.0-beta-3
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 4.0.0-beta-3 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:
- the web site: https://maven.apache.org/
- the maven-user mailing list: https://maven.apache.org/mailing-lists.html
- the reference documentation: https://maven.apache.org/ref/4.0.0-beta-3/
For more information read
https://maven.apache.org/docs/4.0.0-beta-3/release-notes.html
Release Notes - Maven - Version 4.0.0-beta-3
** Bug
* [MNG-8025] - API incompatibility with m-remote-resources-p
* [MNG-8079] - Maven Resolver breaks compatibility due Resolver breakage
* [MNG-8082] - Exceptions of proxied SessionScoped components are not
working correctly
* [MNG-8106] - Maven Metadata corruption if repository directory role
overlaps
* [MNG-8108] - Failure to create the consumer POM
* [MNG-8118] - Dependency-management "client" exclusions overwrite BOM
exclusions
* [MNG-8121] - NullPointerException at
org.apache.maven.artifact.repository.metadata.Metadata.merge
(Metadata.java:293)
* [MNG-8123] - Maven 4.0.0-beta-2 fails with
maven-build-cache-extension 1.2.0
** New Feature
* [MNG-8084] - Make the v4 api usable outside the Maven runtime
** Improvement
* [MNG-8015] - Control the type of path where each dependency can be
placed
* [MNG-8038] - Model builder API
* [MNG-8050] - Same repositories IDs in settings.xml and POM are not
detected
* [MNG-8075] - Allow project.baseUri in repository.url
* [MNG-8081] - default profile activation should consider available
system and user properties
* [MNG-8085] - switch from png+imagemap to svg
* [MNG-8089] - Introduce "fat" type for JAR
* [MNG-8117] - Improve prerequisite evaluation and plugin version
selection logging
* [MNG-8119] - Remove build section in consumer pom profiles
* [MNG-8128] - Custom packaging not found
** Task
* [MNG-8043] - Dependency properties should be provided by Resolver
consumer
* [MNG-8070] - Document Maven Runtime Requirement for Java 17
* [MNG-8073] - Generated XSD files needs to have ASL2.0 license headers
* [MNG-8088] - Apply Resolver ScopeManager
** Dependency upgrade
* [MNG-8091] - Update Resolver to 2.0.0-alpha-10
* [MNG-8102] - Upgrade Parent to 42
* [MNG-8103] - Upgrade default plugin bindings
* [MNG-8105] - Upgrade to JLine 3.26.0
* [MNG-8107] - Upgrade to Resolver 2.0.0-alpha-11
Have fun!
- The Maven TeaM
--0000000000004f4e8006195cb2c4--