Hello,
Currently default Java runtime in Fedora is OpenJDK 8. This is not the latest OpenJDK packaged, but still remains system-default version. Because of that Apache Maven and Apache Ant in Fedora are built using OpenJDK 8 and run on OpenJDK 8.
I am planning to switch Maven 3.6 and Ant 1.10 modules to build with and run on OpenJDK 11, which is the latest LTS release of OpenJDK. This also means that future streams of javapackages-tools module will default to use OpenJDK 11 for building packages. Please let me know if you have any concerns.
-- Mikolaj Izdebski
On 25. 10. 19 19:30, Mikolaj Izdebski wrote:
Hello,
Currently default Java runtime in Fedora is OpenJDK 8. This is not the latest OpenJDK packaged, but still remains system-default version. Because of that Apache Maven and Apache Ant in Fedora are built using OpenJDK 8 and run on OpenJDK 8.
I am planning to switch Maven 3.6 and Ant 1.10 modules to build with and run on OpenJDK 11, which is the latest LTS release of OpenJDK. This also means that future streams of javapackages-tools module will default to use OpenJDK 11 for building packages. Please let me know if you have any concerns.
Hello, I am not very familiar with how Java works in this regard, but since this is the default stream etc., wouldn't it be wise to coordinate such change with a general OpenJDK 11 default Fedora system wide change?
E.g. would the dependent OpenJDK 8 packages still build in stable releases if this change is done globally and for example if Ursa Major/Prime/... is activated?
On Fri, Oct 25, 2019 at 8:47 PM Miro Hrončok mhroncok@redhat.com wrote:
On 25. 10. 19 19:30, Mikolaj Izdebski wrote:
Hello,
Currently default Java runtime in Fedora is OpenJDK 8. This is not the latest OpenJDK packaged, but still remains system-default version. Because of that Apache Maven and Apache Ant in Fedora are built using OpenJDK 8 and run on OpenJDK 8.
I am planning to switch Maven 3.6 and Ant 1.10 modules to build with and run on OpenJDK 11, which is the latest LTS release of OpenJDK. This also means that future streams of javapackages-tools module will default to use OpenJDK 11 for building packages. Please let me know if you have any concerns.
Hello, I am not very familiar with how Java works in this regard, but since this is the default stream etc., wouldn't it be wise to coordinate such change with a general OpenJDK 11 default Fedora system wide change?
It probably would, but I'm not aware of any existing change proposal to switch default OpenJDK versions in Fedora.
E.g. would the dependent OpenJDK 8 packages still build in stable releases if this change is done globally and for example if Ursa Major/Prime/... is activated?
Changing underlying OpenJDK version of maven:3.6 module doesn't change anything with regards to building other packages. Right now nothing build-depends on maven:3.6 module. And if Ursa-Major were enabled in Fedora, most of ursine Java packages would become FTBFS anyway as maven modules are not capable of building packages with. See below for more details.
Since always Maven in Fedora was available in 2 flavors, each having different purposes. "maven" module provides Maven application for end users. This is pure upstream Maven that doesn't "know" how to access libraries packaged as RPMs and included in Fedora. Therefore it is mostly useless for building packages with and I am not aware of any package in Fedora being built with this pure Maven. For purposes of building packages "javapackages-tools" module is available - it provides XMvn - Maven with extensions that enable it to be used for building packages. It also provides RPM macros and other necessary tools which are not available in "maven".
-- Mikolaj Izdebski
any package can switch to jdk11, but sysem jdk should be jdk8, at least for some more time...
On 10/25/19 8:47 PM, Miro Hrončok wrote:
On 25. 10. 19 19:30, Mikolaj Izdebski wrote:
Hello,
Currently default Java runtime in Fedora is OpenJDK 8. This is not the latest OpenJDK packaged, but still remains system-default version. Because of that Apache Maven and Apache Ant in Fedora are built using OpenJDK 8 and run on OpenJDK 8.
I am planning to switch Maven 3.6 and Ant 1.10 modules to build with and run on OpenJDK 11, which is the latest LTS release of OpenJDK. This also means that future streams of javapackages-tools module will default to use OpenJDK 11 for building packages. Please let me know if you have any concerns.
Hello, I am not very familiar with how Java works in this regard, but since this is the default stream etc., wouldn't it be wise to coordinate such change with a general OpenJDK 11 default Fedora system wide change?
E.g. would the dependent OpenJDK 8 packages still build in stable releases if this change is done globally and for example if Ursa Major/Prime/... is activated?
On Sat, Oct 26, 2019 at 9:53 AM Jiri Vanek jvanek@redhat.com wrote:
any package can switch to jdk11, but sysem jdk should be jdk8, at least for some more time...
If anything, we're late to the party of moving to JDK 11 by default. Java 8 has been EOL for a while now.
On 10/26/19 4:33 PM, Neal Gompa wrote:
On Sat, Oct 26, 2019 at 9:53 AM Jiri Vanek jvanek@redhat.com wrote:
any package can switch to jdk11, but sysem jdk should be jdk8, at least for some more time...
If anything, we're late to the party of moving to JDK 11 by default. Java 8 has been EOL for a while now.
Oh this is heavily incorrect. JDK8 is very much alive, and fully supported by upstream. Will be getting all security patches and also many enhancements for several another years.
On Mon, Oct 28, 2019 at 6:04 AM Andrew Dinn adinn@redhat.com wrote:
On 26/10/2019 15:33, Neal Gompa wrote:
If anything, we're late to the party of moving to JDK 11 by default. Java 8 has been EOL for a while now.
Please do not spread misinformation like this. It is very unhelpful.
Okay, sure, paid support continues for two more years, but general (freely available) support for Java 8 ended in January.
For most of us peons, general support EOL is functionally equivalent to full EOL. That's why we end EPEL support on general support EOL dates, and not the more nebulous LTSS EOL dates.
On 28/10/2019 11:38, Neal Gompa wrote:
On Mon, Oct 28, 2019 at 6:04 AM Andrew Dinn adinn@redhat.com wrote:
On 26/10/2019 15:33, Neal Gompa wrote:
If anything, we're late to the party of moving to JDK 11 by default. Java 8 has been EOL for a while now.
Please do not spread misinformation like this. It is very unhelpful.
Okay, sure, paid support continues for two more years, but general (freely available) support for Java 8 ended in January.
What on earth is freely available support? That sounds about as easy to obtain as a unicorn that farts rainbows.
If you mean a version of OpenJDK8 updated with security patches that is free to download and use at your own risk on Linux or Windows then that is still available and will be as long as Red Hat are maintaining their LTS jdk8 releases (several years to go).
You get such a release free with all the usual Linux distros of course (Debian, Ubuntu, Suse etc are all downstream from Red Hat and rely on our code). However, you can also download releases from the AdoptOpenJDK site. Note, those downloads are built by Red Hat's OpenJDK team so you can rely on them being up to date with all the latest security patches and critical fixes.
For most of us peons, general support EOL is functionally equivalent to full EOL. That's why we end EPEL support on general support EOL dates, and not the more nebulous LTSS EOL dates.
I don't know what sort of a peon you are but your pronouncements don't seem to be clarifying the situation. Perhaps you could just let those who are involved in distributing OpenJDK tell people what is and isn't available.
regards,
Andrew Dinn -----------
On Mon, 2019-10-28 at 11:55 +0000, Andrew Dinn wrote: [...]
However, you can also download releases from the AdoptOpenJDK site. Note, those downloads are built by Red Hat's OpenJDK team so you can rely on them being up to date with all the latest security patches and critical fixes.
One clarification. Not *all* builds available at AdoptOpenJDK are being built by Red Hat's OpenJDK team. The builds in question done by us are these specifically:
https://adoptopenjdk.net/upstream.html
Other builds available via the widgets on the landing page[1] are being built on AdoptOpenJDK infra from upstream sources (which they mirror) and some additional (optional) patches on top.
Thanks, Severin
On 10/28/19 12:38 PM, Neal Gompa wrote:
On Mon, Oct 28, 2019 at 6:04 AM Andrew Dinn adinn@redhat.com wrote:
On 26/10/2019 15:33, Neal Gompa wrote:
If anything, we're late to the party of moving to JDK 11 by default. Java 8 has been EOL for a while now.
Please do not spread misinformation like this. It is very unhelpful.
Okay, sure, paid support continues for two more years, but general (freely available) support for Java 8 ended in January.
For most of us peons, general support EOL is functionally equivalent to full EOL. That's why we end EPEL support on general support EOL dates, and not the more nebulous LTSS EOL dates.
Hi Neal, you are really wrong. Openjdk8 is, and will remain fully supported for few next years. We are not speaking about any commercial support, we are speaking about free and open support, provided by project groups, which consists from nearly all oepnjdk8 interested corporations, and namely RH, which is Openjdk8 project lead, and hundreds of community members.
Please really do not spread miss-informations like this. J.
On Fri, 25 Oct 2019 at 18:50, Mikolaj Izdebski mizdebsk@redhat.com wrote:
Hello,
Currently default Java runtime in Fedora is OpenJDK 8. This is not the latest OpenJDK packaged, but still remains system-default version. Because of that Apache Maven and Apache Ant in Fedora are built using OpenJDK 8 and run on OpenJDK 8.
I am planning to switch Maven 3.6 and Ant 1.10 modules to build with and run on OpenJDK 11, which is the latest LTS release of OpenJDK. This also means that future streams of javapackages-tools module will default to use OpenJDK 11 for building packages. Please let me know if you have any concerns.
-- Mikolaj Izdebski _______________________________________________ java-devel mailing list -- java-devel@lists.fedoraproject.org To unsubscribe send an email to java-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject...
I believe this to be fine from Eclipse PoV -- IIRC we've been building against Java 11 upstream for a while now, so all the kinks should be gone.
----- Original Message -----
From: "Mikolaj Izdebski" mizdebsk@redhat.com To: "java-devel" java-devel@lists.fedoraproject.org Cc: maven-owner@fedoraproject.org, "ant-owner" ant-owner@fedoraproject.org, mbooth@fedoraproject.org Sent: Friday, October 25, 2019 1:30:32 PM Subject: Switching Maven and Ant to OpenJDK 11
Hello,
Currently default Java runtime in Fedora is OpenJDK 8. This is not the latest OpenJDK packaged, but still remains system-default version. Because of that Apache Maven and Apache Ant in Fedora are built using OpenJDK 8 and run on OpenJDK 8.
I am planning to switch Maven 3.6 and Ant 1.10 modules to build with and run on OpenJDK 11, which is the latest LTS release of OpenJDK. This also means that future streams of javapackages-tools module will default to use OpenJDK 11 for building packages. Please let me know if you have any concerns.
My concern is what will happen to the libraries in the default module stream? When installing, e.g., dogtag-pki, this brings in the following packages from a default module stream:
apache-commons-cli-0:1.4-4.module_f28+3939+dc18cd75.noarch apache-commons-codec-0:1.11-3.module_f28+3939+dc18cd75.noarch apache-commons-io-1:2.6-3.module_f28+3939+dc18cd75.noarch apache-commons-logging-0:1.2-13.module_f28+3939+dc18cd75.noarch httpcomponents-client-0:4.5.5-4.module_f28+3939+dc18cd75.noarch httpcomponents-core-0:4.4.10-3.module_f28+3939+dc18cd75.noarch
Of these, apache-commons-{cli,codec,io,logging} are all directly required by dogtag-pki, which doesn't yet fully work with JDK-11. (I'm not quite sure how httpcomponents-{client,core} gets pulled in).
Will you continue building these with a target bytecode version for use with JDK8, even though you're building with JDK11? Or are you only building the maven and ant packages with JDK 11 (and not building all libraries in the module with JDK 11)?
Thanks,
- Alex
-- Mikolaj Izdebski
On Mon, Oct 28, 2019 at 1:52 PM Alex Scheel ascheel@redhat.com wrote:
I am planning to switch Maven 3.6 and Ant 1.10 modules to build with and run on OpenJDK 11, which is the latest LTS release of OpenJDK. This also means that future streams of javapackages-tools module will default to use OpenJDK 11 for building packages. Please let me know if you have any concerns.
My concern is what will happen to the libraries in the default module stream? When installing, e.g., dogtag-pki, this brings in the following packages from a default module stream:
This is a valid concern, thanks for bringing it up.
apache-commons-cli-0:1.4-4.module_f28+3939+dc18cd75.noarch apache-commons-codec-0:1.11-3.module_f28+3939+dc18cd75.noarch apache-commons-io-1:2.6-3.module_f28+3939+dc18cd75.noarch apache-commons-logging-0:1.2-13.module_f28+3939+dc18cd75.noarch httpcomponents-client-0:4.5.5-4.module_f28+3939+dc18cd75.noarch httpcomponents-core-0:4.4.10-3.module_f28+3939+dc18cd75.noarchOf these, apache-commons-{cli,codec,io,logging} are all directly required by dogtag-pki, which doesn't yet fully work with JDK-11. (I'm not quite sure how httpcomponents-{client,core} gets pulled in).
Will you continue building these with a target bytecode version for use with JDK8, even though you're building with JDK11? Or are you only building the maven and ant packages with JDK 11 (and not building all libraries in the module with JDK 11)?
These libraries will still be built with JDK <= 8 bytecode, so they should continue to work with JDK 8.
-- Mikolaj Izdebski
java-devel@lists.fedoraproject.org
-
Alex Scheel -
Andrew Dinn -
Jiri Vanek -
Mat Booth -
Mikolaj Izdebski -
Miro Hrončok -
Neal Gompa -
Severin Gehwolf