cstamas commented on code in PR #1827: URL: https://github.com/apache/maven-site/pull/1827#discussion_r4548416783
########## content/markdown/docs/3.10.1/release-notes.md: ########## @@ -0,0 +1,122 @@ +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + +http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +# Maven 3.10.1 Release Notes + +The Apache Maven team would like to announce the release of Maven 3.10.1. + +Maven 3.10.1 is [available for download][0]. + +The core release is independent of plugin releases. Further releases of plugins will be made separately. See the [Plugin list][1] for more information. + +If you have any questions, please consult: + +- the website: [https://maven.apache.org/][2] +- the maven-user mailing list: [https://maven.apache.org/mailing-lists.html](/mailing-lists.html) +- the reference documentation: [https://maven.apache.org/ref/3.10.1/](/ref/3.10.1/) + +## Overview About the Changes + +The main driver for new generation was to align Maven 3 and 4 majors versions on same Resolver version. Hence, Maven 3.10 is now using Resolver 2.0 lineage, same one that is used by Maven 4+. On the other hand, at "Maven level", changes are kept minimal, and upgrading should be pretty straightforward. Also, 3.10 received many security and other enhancements as well. Still, most of the changes happened "under the surface", end users might even be unaware of them. The key changes are listed below. + +Maven 3.10.1 requires Java 8 or above to run, same as the Maven 3.9.x lineage. + +## Notable Changes in Maven 3.10.1 + +Maven 3.10.1 is a bugfix release for 3.10.0. It fixes regressions reported after 3.10.0, backports fixes from Maven 4, and makes startup lighter. + +### New Features and Improvements + +Release 3.10.1 focused on fixing all the regressions, but there are still some features being added: + +- **Optional profiles with `-P ?id`.** Same syntax as Maven 4, so a single command line works for both. +- **Maven 4 `MessageBuilderFactory` for plugins.** Plugins built against `maven-api-core` 4.x can inject `org.apache.maven.api.services.MessageBuilderFactory` on 3.10 and get colored output, the same as on Maven 4. +- **JLine is gone, colors remain.** Maven no longer ships the JLine terminal stack (native libraries, a background setup thread, System.out/err replacement). Colored output is now plain ANSI escape codes, and `maven.style.*` overrides still apply. Startup overhead added in 3.10.0 is gone. JAnsi compatibility is kept through a shim. + +### Regression fixes + +There are way many to list them here, check out full changelog below. + +## Full changelog + +For a full list of changes, please refer to the [GitHub release page](https://github.com/apache/maven/releases/tag/maven-3.10.1). + +## Known issues + +No known issues. + +## Potentially Breaking Core Changes (if migrating from 3.9.x) + +### Stricter POM validation + +Maven 3.10.0 raises the POM validation level: many WARNINGs from the 3.9 lineage (in fact, from the 3.1 lineage) will +now FAIL the build. Things like duplicated dependency entries or duplicated plugin entries will not be tolerated +anymore. This aspect was not changed since Maven 3.1 lineage, and was really time to force users to clean up their +POMs. The checks promoted to errors for the project being built are the 3.1 level ones: duplicated plugins, invalid +characters in a version, malformed snapshot versions and reserved or malformed repository ids. Dependencies keep being +validated at the minimal level (and failure lead to transitive dependencies not being available). +`relativePath` of a parent is validated as well, which no Maven 3.x version did so far. +To temporarily disable the stricter validation add `-Dmaven.resolver.validation=off` to your Maven incovation. Review Comment: ```suggestion To temporarily disable the stricter validation add `-Dmaven.resolver.validation=off` to your Maven invocation. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
