Package Details: jdk7 7u80-1

Git Clone URL: https://aur.archlinux.org/jdk7.git (read-only, click to copy)
Package Base: jdk7
Description: Oracle Java 7 Development Kit (public release - end of support)
Upstream URL: https://www.oracle.com/technetwork/java/archive-139210.html
Keywords: java-environment-jdk java-openjfx java-runtime-headless-jre java-runtime-jre java-web-start-jre
Licenses: custom:Oracle
Provides: java-environment, java-environment-jdk, java-openjfx, java-runtime, java-runtime-headless, java-runtime-headless-jre, java-runtime-jre, java-web-start, java-web-start-jre
Submitter: joschi
Maintainer: severach
Last Packager: severach
Votes: 133
Popularity: 0.139208
First Submitted: 2013-09-11 18:22 (UTC)
Last Updated: 2020-07-23 00:42 (UTC)

Dependencies (10)

Required by (2712)

Sources (7)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »

madscience commented on 2014-10-15 12:19 (UTC)

I second josephgbr's comment. I'm getting this: error: failed to commit transaction (conflicting files) java-environment-common: /usr/bin/appletviewer exists in filesystem java-environment-common: /usr/bin/extcheck exists in filesystem java-environment-common: /usr/bin/idlj exists in filesystem java-environment-common: /usr/bin/jar exists in filesystem java-environment-common: /usr/bin/jarsigner exists in filesystem java-environment-common: /usr/bin/javac exists in filesystem java-environment-common: /usr/bin/javadoc exists in filesystem java-environment-common: /usr/bin/javah exists in filesystem java-environment-common: /usr/bin/javap exists in filesystem java-environment-common: /usr/bin/jcmd exists in filesystem java-environment-common: /usr/bin/jconsole exists in filesystem java-environment-common: /usr/bin/jdb exists in filesystem java-environment-common: /usr/bin/jhat exists in filesystem java-environment-common: /usr/bin/jinfo exists in filesystem java-environment-common: /usr/bin/jmap exists in filesystem java-environment-common: /usr/bin/jps exists in filesystem java-environment-common: /usr/bin/jrunscript exists in filesystem java-environment-common: /usr/bin/jsadebugd exists in filesystem java-environment-common: /usr/bin/jstack exists in filesystem java-environment-common: /usr/bin/jstat exists in filesystem java-environment-common: /usr/bin/jstatd exists in filesystem java-environment-common: /usr/bin/native2ascii exists in filesystem java-environment-common: /usr/bin/rmic exists in filesystem java-environment-common: /usr/bin/schemagen exists in filesystem java-environment-common: /usr/bin/serialver exists in filesystem java-environment-common: /usr/bin/wsgen exists in filesystem java-environment-common: /usr/bin/wsimport exists in filesystem java-environment-common: /usr/bin/xjc exists in filesystem java-runtime-common: /usr/bin/java exists in filesystem java-runtime-common: /usr/bin/keytool exists in filesystem java-runtime-common: /usr/bin/orbd exists in filesystem java-runtime-common: /usr/bin/pack200 exists in filesystem java-runtime-common: /usr/bin/policytool exists in filesystem java-runtime-common: /usr/bin/rmid exists in filesystem java-runtime-common: /usr/bin/rmiregistry exists in filesystem java-runtime-common: /usr/bin/servertool exists in filesystem java-runtime-common: /usr/bin/tnameserv exists in filesystem java-runtime-common: /usr/bin/unpack200 exists in filesystem Errors occurred, no packages were upgraded.

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

@joschi: please set this package to work with 'java-runtime-common' and 'java-environment-common'

Det commented on 2014-10-13 03:02 (UTC)

You didn't reply to my email sent almost a month ago about cleaning up the Java packages. Are you still alive?

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.

galaux commented on 2014-10-05 13:16 (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.

tsachev commented on 2014-10-02 16:37 (UTC)

please copy the src.zip file to /usr/lib/jvm/java-7-oracle

tsachev commented on 2014-10-02 16:16 (UTC)

I do not think that (jmc) mission control is included in jdk7. isn't it only in the java 8 package? And merging with jdk7 will be very good. It is annoying to have jdk for java 8 and jdk7-oracle for java 7.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »