Bukama commented on code in PR #759: URL: https://github.com/apache/maven-site/pull/759#discussion_r2051552411
########## content/markdown/guides/mini/guide-migration-to-mvn4.md: ########## @@ -0,0 +1,339 @@ +# Migrate to Maven 4 + +<!-- +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 4 introduces several upgrades and improvements (see ["What's new in Maven 4?"](/whatsnewinmaven4.html)). +Some of them are backwards compatible or optional, but some require changes of your build environment or Maven project. +This page offers help for users who want to build their projects with Maven 4. + +In short, the general suggestion for the migration is to do it in three steps: + +1. Meet the prerequisites +2. Use Maven 4 for your build and fix build errors +3. Introduces optional Maven 4 features + +If you run into any issues, please don't hesitate to contact the [users mailing list](/mailing-lists.html). +The Maven team is interested in all your migration experiences - either good or bad! + +**Notes**: + +* This page will constantly be updated to contain changes, but also to integrate feedback of the community and their experience when upgrading to Maven 4. + This means it will still receive updates after Maven 4 was already released. +* It is planed to provide a migration tool (see [MNG-8649](https://issues.apache.org/jira/projects/MNG/issues/MNG-8649)), doing most of the steps needed to migrate a project. Review Comment: > Related: do we want to provide such a tool from our side, or can we team up with OpenRewrite? They might already have something in the making. @gnodet wrote in Slack, that he wanted to provide it from our side, because he thinks OpenRewrite will be to limited -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
