Replying to some previous comments:
* OpenJDK 21 is the last version to support Java 8 AFAIK.
* Indeed it is possible to compile projects using the system JDK
together with the -target + -source / --release flags.
* In the spirit of "staying close to the upstream", the our (Maven)
ecosystem
On Thu, May 2, 2024 at 9:24 PM Kevin Kofler via devel
wrote:
>
> Christopher wrote:
> > So, I actually think that building with the *latest* JDK that we ship,
> > and using the `--release` flag during compilation is actually safer
> > than building against the lowest that we support, because it
Sorry, with "package" I mean a *new* package for jdk 17, depending on a
lib built and tested only for jdk 8 to 11. Basically, that metadata in
the rpm for the lib would not have that runtime information for any new
package wanting to depend on it targeted for jdk 17.
On 5/2/24 18:35, Kevin
Carlos Rodriguez-Fernandez wrote:
> How could that be expressed so that those are caught quickly at build
> time? Someone wants to depend on a java lib that has been tested only in
> JRE 8 to 11, but wants to build the package with JRE 17+, or vice-versa,
> for example. Perhaps, the only feasible
Christopher wrote:
> So, I actually think that building with the *latest* JDK that we ship,
> and using the `--release` flag during compilation is actually safer
> than building against the lowest that we support, because it is most
> likely to strictly enforce correct byte code generation for the
I have dealt with bugs where a library runs well in JRE 11, but crashes
when run in JRE 17 because the InetSocketAddress implementation changed.
Totally unrelated with the language features or bytecode versions.
Nevertheless, even in that case, if I bring in that library from the
distro repo,
On Thu, May 2, 2024 at 6:59 AM Kevin Kofler via devel
wrote:
>
> Carlos Rodriguez-Fernandez wrote:
> > Regarding the proposal as a whole, I think the proposal idea makes a lot
> > of sense, but for apps depending on system jar libraries, there should
> > be a way to specify that the app depends
Carlos Rodriguez-Fernandez wrote:
> Regarding the proposal as a whole, I think the proposal idea makes a lot
> of sense, but for apps depending on system jar libraries, there should
> be a way to specify that the app depends on a specific java bytecode
> version range. System libraries packages
/Drop_Mandatory_Requires_on_JRE
Announced -
https://discussion.fedoraproject.org/t/f41-change-proposal-drop-mandatory-requires-on-jre-system-wide/114186
[snip]
=== Context ===
Java packages are compiled using `javac` into `.class` files and
composed into `.jar` archives. Jar archives can be used
On 25. 4. 2024 17:46, Michel Lind wrote:
On 4/24/24 11:14 AM, Aoife Moloney wrote:
Wiki -
https://fedoraproject.org/wiki/Changes/Drop_Mandatory_Requires_on_JRE
Announced -
https://discussion.fedoraproject.org/t/f41-change-proposal-drop-mandatory-requires-on-jre-system-wide/114186
[snip
On 4/24/24 11:14 AM, Aoife Moloney wrote:
Wiki - https://fedoraproject.org/wiki/Changes/Drop_Mandatory_Requires_on_JRE
Announced -
https://discussion.fedoraproject.org/t/f41-change-proposal-drop-mandatory-requires-on-jre-system-wide/114186
[snip]
=== Context ===
Java packages
Wiki - https://fedoraproject.org/wiki/Changes/Drop_Mandatory_Requires_on_JRE
Announced -
https://discussion.fedoraproject.org/t/f41-change-proposal-drop-mandatory-requires-on-jre-system-wide/114186
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part
Wiki - https://fedoraproject.org/wiki/Changes/Drop_Mandatory_Requires_on_JRE
Announced -
https://discussion.fedoraproject.org/t/f41-change-proposal-drop-mandatory-requires-on-jre-system-wide/114186
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part
13 matches
Mail list logo
