Portable Openjdk

[Rosalia Hollingworth]

Uninstallingany of them did not work. Uninstalling all of them did not work because they were required by several programs. Explicitly re-installing any of them did not work. The only solution was to first uninstall all programs that require Java, then uninstall all openjdk packages, then re-install jdk-openjdk, then re-install the programs requiring Java.

As you can see, the latest version of logisim requires java-runtime, which can be provided by either jdk17-openjdk or jre17-openjdk (any one of those packages listed inside the parenthesis will provide the java-runtime)

First I thought it's strange that there's no link to a bug tracker on the OpenJDK project page, then I found bugs.openjdk.java.net, but it's only for accredited project members. How do people outside the ivory tower contribute issues? There's the mailing list and some people call sending issues and patches to a mailing list bug tracking... but the development and usage of bug tracker contradicts.

My interpretation of their FAQ is that this will be triaged by an Oracle engineer, and if accepted it will be assigned a number and (usually) become visible in both Oracles + the OpenJDK bug databases.

It would be really helpful if this info/link were on the OpenJDK bug page too. The database split is already confusing enough - when your goal is to contribute to OpenJDK but you find yourself at an Oracle-branded page, it seems like you've gone to the wrong place.

File a new incident with the subject line "Additional information to JDK-XXXXXXX'. Replace XXXXXXX with the reference number received when the report is filed. We are working on a system where you will be able to provide additional information to the existing bug.

A Contributor is a Participant who has signed the Oracle Contributor Agreement (OCA), or who works for an organization that has signed that agreement or its equivalent and makes contributions within the scope of that work and subject to that agreement. A Contributor may submit changes larger than a simple patch, may propose new Projects, and may take on various roles within Groups and Projects.

A Participant is an individual who has subscribed to one or more OpenJDK mailing lists. A Participant may post messages to a list, submit simple patches, and make other kinds of small contributions.

This post shares the links to the actual cause of the conflict related to the jdk-openjdk, jre-openjdk and jre-openjdk-headless. As of 2023-11-02 you have to make a choice of which of them you need. The link also has the actions to take to solve your situation.

I originally installed using installation package at version 5.2.5.20. JAVA_HOME is empty, so guessing configuration is using a set path potentially? Looked to maybe set all the java paths and see if it changes it but wanted to get some input before doing so on what might be best practices.

Quick question here as I posted separately and have not heard anything back. If we used the installer initial to setup lucee in a Oracle Linus environment, it used Oracle java 8. But I am working to update it to run OpenJDK 11 and have installed it using yum. (yum install java-11-openjdk) How do I now tell lucee to use OpenJDK instead of Oracle? JAVA_HOME is empty on my current install and if I add it, Lucee still uses Oracle.

Can get running now fine using OpenJDK 8. However running into several issues with Lucee starting using OpenJDK 11. At least here I can get current updates installed, but would like to plan an update to version 11 at some point in the future.

-Djava.endorsed.dirs=/opt/lucee/tomcat/endorsed is not supported. Endorsed standards and standalone APIs

in modular form will be supported via the concept of upgradeable modules.

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

This happens likely because another package on your system is depending on Java. While removing openjdk-7-jre, apt-get sees that if it uninstalls OpenJDK, some packages will have unmet dependencies. To solve this, it installs another package which provides Java.

This indicates that all the LibreOffice packages are depending on openjdk-7-jre. As long as these packages are installed, OpenJDK cannot be uninstalled without installing an alternate Java automatically.

This takes all of the Oracle Java utilities that you've previously extracted, and gives them the first priority, in case you have other versions of Java installed. (since Ubuntu allows you to have multiple versions of the same utility installed)

Along with the rest of answers - have you checked your .bashrc file to make sure that JAVA_HOME environment is not there? Removing that line should do the trick in freeing your Ubuntu from openjdk. Like an example:

cimg/openjdk is a Docker image created by CircleCI with continuous integration builds in mind.Each tag contains a version of OpenJDK, the Java Development Kit and any binaries and tools that are required for builds to complete successfully in a CircleCI environment.

In the above example, the CircleCI OpenJDK Docker image is used for the primary container.More specifically, the tag 21.0.2 is used meaning the version of OpenJDK will be v21.0.2.You can now use OpenJDK within the steps for this job.

- The version of OpenJDK to use.This can be a full SemVer point release (such as 11.0.2) or just the minor release (such as 11.0).If you use the minor release tag, it will automatically point to future patch updates as they are released by AdoptOpenJDK & Oracle.For example, the tag 11.0 points to OpenJDK v11.0.5 now, but when the next release comes out, it will point to OpenJDK v11.0.6.

The browsers variant is the same OpenJDK image but with Node.js, Selenium, and browser dependencies pre-installed via apt.The browsers variant can be used by appending -browser to the end of an existing cimg/openjdk tag.The browsers variant is designed to work in conjunction with the CircleCI Browser Tools orb.You can use the orb to install a version of Google Chrome and/or Firefox into your build. The image contains all of the supporting tools needed to use both the browser and its driver.

I was also trying to build openjdk-8 within the meta-java layer for the zeus branch (on Ubuntu 16.04) and found this thread because I encountered the same issues. I was finally able to successfully build after the following steps:

The Java Runtime Environment (JRE) is required to run Java programs. Nowadays there are many JRE packages available from a variety of projects and companies, but the two most popular on Ubuntu are OpenJDK and Oracle HotSpot. Using one package over the other should not create any functional difference in most applications; however, some prefer OpenJDK over Oracle HotSpot as the former does not contain closed-source components, has a much clearer licensing and support policy, and is maintained as part of the Ubuntu archive, with easier installation and upgrades.

With new versions of Java released every 6 months, there are multiple versions available for use. Nowadays, Java 11 is the current Long Term Support (LTS) version, but Java 8 is still widely used. Moreover, the non LTS versions of Java are bringing a steady stream of innovation into the language, and also see some adoption.

Ubuntu offers the default-jre package, which is regularly updated to ship the latest version of the current OpenJDK JRE in Long Term Support (LTS). The default-jre is an excellent choice for most situations, thanks to the outstanding track of backwards compatibility of the Java Virtual Machine.

(Alternatively, you may opt to use a specific Java version, using for example the openjdk-11-jre package; as updates are released for that version of the Java Virtual Machine, that packages will be updated, allowing you to stick to the latest and greatest update of one specific version of the Java language.)

Hello, I'm using Elasticsearch on Arch Linux, version 8.7.0, but this latest version use jre19 openjdk that reached its EOL ( Java/OpenJDK endoflife.date) so, on Arch Linux it cannot be installed anymore because this dependency has been removed from Arch repositories. If I'm not wrong, Elasticsearch 8.7.1 should use JRE OpenJDK 20, but on GitHub project page it is not still released.

Each Elasticsearch distribution comes bundled with its own JDK, and that's the one we recommend to use. It should not depend on an external JDK so it should be unaffected by the fact that this version is now technically EOL.

Thank you @DavidTurner I'm just concerned to use a dependency that reached EOL mostly for security concerns. This is the main reason I would prefer to avoid it. Your answer is efficient and thank you for the support matrix link. I hope the new version of Elasticsearch will be released asap with bundled Java 20.

That's the advantage of using the bundled version: it's not a dependency that you need to track separately. It's just part of the product, similarly to Lucene and Log4J and Jackson and all the other libraries on which Elasticsearch depends. Elastic looks after the security side of things, so a vulnerability(*) in the bundled JDK would be reported as an Elastic Security Advisory.

(*) NB not all vulnerabilities reported in a dependency are vulnerabilities in the dependent product. For instance most Elasticsearch releases were not vulnerable to the famous Log4J bug reported in CVE-2021-44228. Similarly, there have been a number of Jackson vulnerabilities that did not affect Elasticsearch because Elasticsearch did not use the vulnerable features in the library.

3a8082e126