(Initial page) |
(announcing the change) |
||
(4 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
Line 22: | Line 16: | ||
* Name: [[User:Mizdebsk|Mikolaj Izdebski]] | * Name: [[User:Mizdebsk|Mikolaj Izdebski]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: < | * Email: <mizdebsk@redhat.com> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
Line 29: | Line 23: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAnnounced]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Line 47: | Line 41: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* [ | * [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/PU5RHOATCJ6X3HAY37IHGMPU6NXJD5XR/ Announced] | ||
* [ | * [https://discussion.fedoraproject.org/t/f43-change-proposal-maven-4-system-wide/145921 Discussion thread] | ||
* FESCo issue: <will be assigned by the Wrangler> | * FESCo issue: <will be assigned by the Wrangler> | ||
* Tracker bug: <will be assigned by the Wrangler> | * Tracker bug: <will be assigned by the Wrangler> | ||
Line 59: | Line 53: | ||
Maven 4.0.0-rc-2 has been released in December 2024. | Maven 4.0.0-rc-2 has been released in December 2024. | ||
Final 4.0.0 version is expected to be released in year 2025. | Final 4.0.0 version is expected to be released in year 2025. | ||
In case the final version 4.0.0 is not released in time before Fedora 43 change completion deadline, a release candidate version will be included in Fedora 43 and may be updated to a newer version later in Fedora 43 lifecycle. | In case the final version 4.0.0 is not released in time before Fedora Linux 43 change completion deadline, a release candidate version will be included in Fedora Linux 43 and may be updated to a newer version later in Fedora Linux 43 lifecycle. | ||
The goal of this change is to package Maven 4 and make it available as alternative to Maven 3 in Fedora 43. | The goal of this change is to package Maven 4 and make it available as alternative to Maven 3 in Fedora Linux 43. | ||
It is not a goal to replace Maven 3, Maven 3 will continue to be available to users. | It is not a goal to replace Maven 3, Maven 3 will continue to be available to users. | ||
Line 106: | Line 100: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** package [https://src.fedoraproject.org/rpms/maven4 maven4] and all of its dependencies and make them available in Fedora 43 | ** package [https://src.fedoraproject.org/rpms/maven4 maven4] and all of its dependencies and make them available in Fedora Linux 43 | ||
** ensure that all [https://src.fedoraproject.org/tests/maven maven tests] are passing, including upstream integration tests (core ITs) | ** ensure that all [https://src.fedoraproject.org/tests/maven maven tests] are passing, including upstream integration tests (core ITs) | ||
** ensure that maven4 package works in parallel with maven | ** ensure that maven4 package works in parallel with maven | ||
Line 134: | Line 128: | ||
== Early Testing (Optional) == | == Early Testing (Optional) == | ||
<!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. --> | <!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. --> | ||
== How To Test == | == How To Test == |
Latest revision as of 17:47, 24 February 2025
Maven 4
Summary
Add Apache Maven 4 to Fedora Linux 43 as parallel-installable alternative to Maven 3.
Owner
- Name: Mikolaj Izdebski
- Email: <mizdebsk@redhat.com>
Current status
- Targeted release: Fedora Linux 43
- Last updated: 2025-02-24
- Announced
- Discussion thread
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Maven 4 is a new major version of Maven after 15 years of Maven 3. It brings many improvements, but also breaking changes.
Maven 4.0.0-rc-2 has been released in December 2024. Final 4.0.0 version is expected to be released in year 2025. In case the final version 4.0.0 is not released in time before Fedora Linux 43 change completion deadline, a release candidate version will be included in Fedora Linux 43 and may be updated to a newer version later in Fedora Linux 43 lifecycle.
The goal of this change is to package Maven 4 and make it available as alternative to Maven 3 in Fedora Linux 43.
It is not a goal to replace Maven 3, Maven 3 will continue to be available to users.
It is not a goal of this change to build Fedora packages with Maven 4 - XMvn, %mvn_build etc. will continue to use Maven 3. Switching Java packaging tools to use Maven 4 is planned in the future and a separate system-wide change proposal is expected be submitted for that effort, targeting a future Fedora Linux version newer than 43.
Feedback
Benefit to Fedora
Java software developers will be able to use the latest version of the most popular Java development tool.
Fedora packagers will be able to start packaging Maven 4 plugins and extensions in preparation for switching Fedora packages to be built with Maven 4 by default in the future.
Scope
- Proposal owners:
- package maven4 and all of its dependencies and make them available in Fedora Linux 43
- ensure that all maven tests are passing, including upstream integration tests (core ITs)
- ensure that maven4 package works in parallel with maven
- Other developers: N/A (not needed for this Change)
- Release engineering: N/A (not needed for this Change)
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy: N/A (not needed for this Change)
Upgrade/compatibility impact
Maven 4 will be added as a new package, parallel-installable with Maven 3. Existing users and systems with Maven 3 installed won't be affected by this change.
Early Testing (Optional)
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)