Package Details: jre 23.0.1-1

Git Clone URL: https://aur.archlinux.org/jdk.git (read-only, click to copy)
Package Base: jdk
Description: Oracle Java Runtime Environment
Upstream URL: https://www.oracle.com/java/
Licenses: LicenseRef-custom
Conflicts: jdk
Provides: java-runtime, java-runtime-headless, java-runtime-headless-jdk, java-runtime-jdk23, jre23-jdk, jre23-jdk-headless
Submitter: td123
Maintainer: dbermond
Last Packager: dbermond
Votes: 1087
Popularity: 0.90
First Submitted: 2011-08-27 17:56 (UTC)
Last Updated: 2024-11-16 14:08 (UTC)

Dependencies (12)

Required by (1733)

Sources (9)

Pinned Comments

dbermond commented on 2024-03-19 19:54 (UTC)

  • Important notice:

As was made with the java packages in the official repositories, jdk now provides the jre alongside it, and both packages conflict with each other. During the package upgrade to version 22, act accordingly to your needs. For example, if you have both jdk and jre installed, only jdk will be sufficient, as it now also contains the runtime environment, and jre can be uninstalled. If you have only jre installed, no action is required.

Latest Comments

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 81 Next › Last »

Commander commented on 2014-10-13 16:11 (UTC)

@Det Um the dependencies are wrong no? It should now be changed as galaux said. change your "java-runtime" providing package dependency from "java-common" to "java-runtime-common" Are the other things with JAVA_HOME etc fixed in this pkgbuild?

Det commented on 2014-10-13 15:16 (UTC)

I surely can, see the explanation from galaux just before your comment.

Det commented on 2014-10-13 15:15 (UTC)

I will, that was asked and explained in the comment just before yours, thank-you :).

rafaelff commented on 2014-10-13 15:13 (UTC)

@det: please set this package to work with 'java-runtime-common' and 'java-environment-common'. Thanks in advance!

KingYes commented on 2014-10-13 06:42 (UTC)

I can't upgrade my system cuz this package: :: Replace java-common with extra/java-runtime-common? [Y/n] Y resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: jdk: requires java-common Can you fixes it for me?

galaux commented on 2014-10-12 20:00 (UTC)

As previously reported, package "java-common" is now gone in favor of "java-runtime-common" and "java-environment-common". @users: once this very package is updated, you will be able to build and install it. Please note that a news item was posted (https://www.archlinux.org/news/java-users-manual-intervention-required-before-upgrade/) that provides 3 quick commands to prevent you from getting a "file conflict" error during the next pacman upgrade. Please see our Java wiki page for info, and forum, IRC, Mailing lists for help. @maintainer: you will need to: - change your "java-runtime" providing package dependency from "java-common" to "java-runtime-common" - add dependency "java-environment-common" to your "java-environment" providing packages Changelog: - Links from /usr/bin now belong to one of the mentioned "common" packages (fixes FS#41883) - Links from /usr/bin point at /usr/lib/jvm/default/bin/* and thus do not use JAVA_HOME nor script /usr/lib/java-common-wrapper (prevents incorrect Java path detection for many build or run scripts). As a side effect, forcing a Java runtime by setting JAVA_HOME is now NOT supported anymore. This should be all. Please have a look at official OpenJDK packages from extra for reference. "install" scripts for OpenJDK packages have also been revamped for nicer integration but without any consequence on other packages. These could easily be customized (or even taken "as is") for your own "install" scripts.

galaux commented on 2014-10-12 19:59 (UTC)

As previously reported, package "java-common" is now gone in favor of "java-runtime-common" and "java-environment-common". @users: once this very package is updated, you will be able to build and install it. Please note that a news item was posted (https://www.archlinux.org/news/java-users-manual-intervention-required-before-upgrade/) that provides 3 quick commands to prevent you from getting a "file conflict" error during the next pacman upgrade. Please see our Java wiki page for info, and forum, IRC, Mailing lists for help. @maintainer: you will need to: - change your "java-runtime" providing package dependency from "java-common" to "java-runtime-common" - add dependency "java-environment-common" to your "java-environment" providing packages Changelog: - Links from /usr/bin now belong to one of the mentioned "common" packages (fixes FS#41883) - Links from /usr/bin point at /usr/lib/jvm/default/bin/* and thus do not use JAVA_HOME nor script /usr/lib/java-common-wrapper (prevents incorrect Java path detection for many build or run scripts). As a side effect, forcing a Java runtime by setting JAVA_HOME is now NOT supported anymore. This should be all. Please have a look at official OpenJDK packages from extra for reference. "install" scripts for OpenJDK packages have also been revamped for nicer integration but without any consequence on other packages. These could easily be customized (or even taken "as is") for your own "install" scripts.

galaux commented on 2014-10-12 19:59 (UTC)

As previously reported, package "java-common" is now gone in favor of "java-runtime-common" and "java-environment-common". @users: once this very package is updated, you will be able to build and install it. Please note that a news item was posted (https://www.archlinux.org/news/java-users-manual-intervention-required-before-upgrade/) that provides 3 quick commands to prevent you from getting a "file conflict" error during the next pacman upgrade. Please see our Java wiki page for info, and forum, IRC, Mailing lists for help. @maintainer: you will need to: - change your "java-runtime" providing package dependency from "java-common" to "java-runtime-common" - add dependency "java-environment-common" to your "java-environment" providing packages Changelog: - Links from /usr/bin now belong to one of the mentioned "common" packages (fixes FS#41883) - Links from /usr/bin point at /usr/lib/jvm/default/bin/* and thus do not use JAVA_HOME nor script /usr/lib/java-common-wrapper (prevents incorrect Java path detection for many build or run scripts). As a side effect, forcing a Java runtime by setting JAVA_HOME is now NOT supported anymore. This should be all. Please have a look at official OpenJDK packages from extra for reference. "install" scripts for OpenJDK packages have also been revamped for nicer integration but without any consequence on other packages. These could easily be customized (or even taken "as is") for your own "install" scripts.

Det commented on 2014-10-05 13:34 (UTC)

Thanks for letting me know. :)

galaux commented on 2014-10-05 13:15 (UTC)

FYI, current package "java-common" will be split due to https://bugs.archlinux.org/task/41883 The only changes needed will be: - for java-runtime-headless providing packages to now depend on "java-runtime-common" rather than "java-common" - for java-environment providing packages to now depend on "java-environment-common" These new packages are expected to be pushed to extra next week-end.

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 81 Next › Last »