From Fedora Project Wiki
No edit summary
mNo edit summary
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
<!-- 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 -->



Revision as of 07:07, 24 February 2025


Maven 4

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Add Apache Maven 4 to Fedora Linux 43 as parallel-installable alternative to Maven 3.

Owner


Current status

  • Targeted release: Fedora Linux 43
  • Last updated: 2025-02-24
  • [<link to devel-announce post will be added by Wrangler> Announced]
  • [<will be assigned by the Wrangler> 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)

Release Notes