Changes/Deprecate Apache Maven 2.x

Deprecate Apache Maven 2.x

Summary

Mark Apache Maven 2.x software packages as deprecated.

Owner

• Name: Mikolaj Izdebski
• Email: mizdebsk@redhat.com
• Release notes owner:

Current status

• Targeted release: Fedora 30
• Last updated: 2019-01-07
• Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The last upstream release of Apache Maven 2.x was in November 2009, more than 9 years ago. Upstream declares that this version of Maven has reached its end of life, is no longer supported and that security vulnerability reports will not be addressed . The next major version, Maven 3, is available in Fedora 15 and later since year 2010.

Apache Maven 2.x software packages are intended to be eventually removed from Fedora, but are kept in Fedora for some additional, indeterminate time for various reasons including maintaining backwards compatibility. In order to prevent new packages from depending on these packages, they are marked as deprecated.

As of time of submilsion of this change proposal, 75 Fedora components still Require or BuildRequire Apache Maven 2.x packages, therefore immediate retirement of these packages is not feasible at this point.

Benefit to Fedora

Packages of obsolete Apache Maven 2.x software will be clearly and explicitly marked as deprecated. Other packages in Fedora will not be able to add dependencies on deprecated packages (that includes Requires, BuildRequires, Recommends, Suggests, etc.). This applies both for updates of existing packages and new packages added to Fedora. This in turn will make it easier to gradually remove dependencies on deprecated packages and finally remove deprecated Apache Maven 2.x software from Fedora.

Scope

• Proposal owners: add special virtual provides deprecated() to all packages built from maven2 source component.

• Other developers: N/A (not a System Wide Change)

• Release engineering: #7990
  • List of deliverables: N/A (not a System Wide Change)

• Policies and guidelines: N/A (not a System Wide Change)

• Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

No change in user experience. Technically, nothing changes; deprecated packages work and behave as before.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

• Contingency mechanism: 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)

Documentation

N/A (not a System Wide Change)