From Fedora Project Wiki
No edit summary
(adding release notes tracker)
 
(12 intermediate revisions by 2 users not shown)
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/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.'''}}


Line 4: Line 5:


{{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].}}
{{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 -->
Line 9: Line 11:
= Drop Mandatory Requires on JRE =
= Drop Mandatory Requires on JRE =


{{Change_Proposal_Banner}}
 


== Summary ==
== Summary ==
Line 28: Line 30:


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF41]]
<!-- 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 46: Line 48:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* [<will be assigned by the Wrangler> devel thread]
* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/MPQ76CVP53Z4SBTGIPV3V5S76CBUKRMJ/ Announced]
* FESCo issue: <will be assigned by the Wrangler>
* [https://discussion.fedoraproject.org/t/f41-change-proposal-drop-mandatory-requires-on-jre-system-wide/114186 Discussion Thread]
* Tracker bug: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/3207 #3207]
* Release notes tracker: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2282167 #2282167]
 
* Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/103 #103]
== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Line 63: Line 65:


Java packages, which serve as libraries only, lack the `main` method and are not executable. Therefore, there is no requirement on any specific JRE imposed by the library implicitly.
Java packages, which serve as libraries only, lack the `main` method and are not executable. Therefore, there is no requirement on any specific JRE imposed by the library implicitly.
=== Different JDKs ===
This proposal is also related to the topic of different JDKs. Developers may want to use or build packages which use a JDK different than the one provided by the `java-<N>-openjdk` package. After this proposal was implemented, they would be able to depend on Java library packages with no introduction of the OpenJDK package.
=== Rationale ===
Java libraries are more similar to native libraries than to libraries written in dynamic scripting languages. They are compiled to a bytecode and are not executable. Java libraries can be used as dependencies for any Java application and there is no implicit dependency on the system default JDK.
Java applications, on the other hand, are expected to be tested and to work with the system JDK and from the user's perspective: after installing an application they must be able to simply run the binary. Therefore the `Requires` on the system JDK is kept for Java applications.


== Feedback ==
== Feedback ==
Line 98: Line 108:
* Reduced dependencies of Java packages.
* Reduced dependencies of Java packages.
* Simplified maintenance of Java packages.
* Simplified maintenance of Java packages.
** Smaller impact of JDK major updates (e.g. `1.8.0 -> 11 -> 17 -> 21`)
** Smaller impact of JDK major updates (e.g. `1.8.0 -> 11 -> 17 -> 21`). Introducing a new system version of JDK requires the rebuild of each Java package in order to have updated `Requires` to contain the newest version.


== Scope ==
== Scope ==
Line 104: Line 114:
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
** Find all Java applications in Fedora, i.e. packages which `BuildRequire` `java-devel / maven-local / ant` and at the same time install files into `/bin` or `/sbin` or `/usr/bin` or `/usr/sbin`.
** Find all Java applications in Fedora, i.e. packages which `BuildRequire` `java-devel / maven-local / ant` and at the same time install files into `/bin` or `/sbin` or `/usr/bin` or `/usr/sbin`.
** Add `Requires: java-headless` into their `.spec` file.
** Open pull requests adding `Requires: java-headless` into their `.spec` file.
** Remove `Requires` generator from [https://src.fedoraproject.org/rpms/javapackages-tools/blob/8714cc1d03d3f31251539c3fca53383b822834bc/f/javapackages-config.json#_5 javapackages-tools]
** Remove `Requires` generator from [https://src.fedoraproject.org/rpms/javapackages-tools/blob/8714cc1d03d3f31251539c3fca53383b822834bc/f/javapackages-config.json#_5 javapackages-tools]
** Wait for a mass rebuild.
** Wait for a mass rebuild.
Line 110: Line 120:
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
** Maintainers of Java applications will need to add an explicit `Requires: java-headless` field into their `.spec` file or a specific version of `java`.
** Maintainers of Java applications will need to add an explicit `Requires: java-headless` field into their `.spec` file or a specific version of thereof (such as `java-17-openjdk-headless`).


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/12069 #12069] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
Line 119: Line 129:
* Policies and guidelines:
* Policies and guidelines:
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
** Guidelines need to be [https://pagure.io/packaging-committee/pull-request/1360 modified].
** Guidelines need to be modified ([https://pagure.io/packaging-committee/pull-request/1360 open Pull Request]).


* Trademark approval: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


* Alignment with Community Initiatives:  
* Alignment with Community Initiatives: N/A
<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->
<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->


Line 173: Line 183:
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
* `javapackages-tools`
* `javapackages-tools`
** This change allows the removal of a `Requires` generator.
** This change allows the removal of the `Requires` generator.


== Contingency Plan ==
== Contingency Plan ==

Latest revision as of 16:44, 2 October 2024


Drop Mandatory Requires on JRE

Summary

Drop the requirement of Java libraries to have Requires on JREs.

Owner

Current status

Detailed Description

Current guidelines require all Java packages to Require: java-headless or java-headless >= 1:minimal_required_version.

Our aim is to drop this explicit requirement on Java library packages. The requirement should stay for Java applications.

Context

Java packages are compiled using javac into .class files and composed into .jar archives. Jar archives can be used as compile or runtime dependencies for other packages or can be directly executed with the java command provided by a JRE.

Jar archives can be executed using the command: java -jar ${FILE}. This command executes the main method either specified via CLI or specified within the Jar manifest file.

Java packages, which serve as libraries only, lack the main method and are not executable. Therefore, there is no requirement on any specific JRE imposed by the library implicitly.

Different JDKs

This proposal is also related to the topic of different JDKs. Developers may want to use or build packages which use a JDK different than the one provided by the java-<N>-openjdk package. After this proposal was implemented, they would be able to depend on Java library packages with no introduction of the OpenJDK package.

Rationale

Java libraries are more similar to native libraries than to libraries written in dynamic scripting languages. They are compiled to a bytecode and are not executable. Java libraries can be used as dependencies for any Java application and there is no implicit dependency on the system default JDK.

Java applications, on the other hand, are expected to be tested and to work with the system JDK and from the user's perspective: after installing an application they must be able to simply run the binary. Therefore the Requires on the system JDK is kept for Java applications.

Feedback

Benefit to Fedora

  • Very little user-visible benefit.
  • Reduced dependencies of Java packages.
  • Simplified maintenance of Java packages.
    • Smaller impact of JDK major updates (e.g. 1.8.0 -> 11 -> 17 -> 21). Introducing a new system version of JDK requires the rebuild of each Java package in order to have updated Requires to contain the newest version.

Scope

  • Proposal owners:
    • Find all Java applications in Fedora, i.e. packages which BuildRequire java-devel / maven-local / ant and at the same time install files into /bin or /sbin or /usr/bin or /usr/sbin.
    • Open pull requests adding Requires: java-headless into their .spec file.
    • Remove Requires generator from javapackages-tools
    • Wait for a mass rebuild.
  • Other developers:
    • Maintainers of Java applications will need to add an explicit Requires: java-headless field into their .spec file or a specific version of thereof (such as java-17-openjdk-headless).
  • Release engineering: #12069
    • Mass rebuild is not required, this change can propagate via natural rebuilds.
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Community Initiatives: N/A

Upgrade/compatibility impact

  • For Java libraries:
    • This change is removing Requires and therefore users manually installing a Java library will not additionally install the JVM.
  • For Java applications:
    • After fully implemented, applications will no longer be installable along with any JVM but rather only the system one (unless the package maintainer decides otherwise)

How To Test

  • Installing a Java library should not typically install JVM (but can if the library depends on a Java application)
  • Installing a Java application MUST cause the installation of the system-wide JVM (or a different version thereof)
  • Executing a binary installed in typical locations (such as /usr/bin) MUST NOT cause an error related to the JVM not being installed.

User Experience

Users with no Java application installed, but some Java libraries installed: the JVM may be automatically uninstalled as it is possibly not required by anything.

It is possible that there are users with only some older JVM installed. The following depends on the decision of each Java application package maintainer, but the general expectation is that the system-wide JVM will be installed and the older JVM will no longer be required by other packages.

Users who explicitly installed JVMs of various versions: no change.

Dependencies

  • javapackages-tools
    • This change allows the removal of the Requires generator.

Contingency Plan

  • Contingency mechanism:
    • In case of unexpected problems, the Requires generators can be reintroduced into javapackages-tools and packages can be rebuilt.
  • Contingency deadline: Branch Fedora Linux 41 from Rawhide Tue 2024-08-06
  • Blocks release? No

Documentation

No documentation outside of this document.

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Drop_Mandatory_Requires_on_JRE&oldid=721302"