Package Details: jdk7 7u80-1

Git Clone URL: https://aur.archlinux.org/jdk7.git (read-only)
Package Base: jdk7
Description: Oracle Java 7 Development Kit (public release - end of support)
Upstream URL: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Keywords: java-environment-jdk java-openjfx java-runtime-headless-jre java-runtime-jre java-web-start-jre
Licenses: custom
Provides: java-environment=7, java-environment-jdk=7, java-openjfx=7, java-runtime=7, java-runtime-headless=7, java-runtime-headless-jre=7, java-runtime-jre=7, java-web-start=7, java-web-start-jre=7
Submitter: joschi
Maintainer: severach
Last Packager: Det
Votes: 136
Popularity: 0.164154
First Submitted: 2013-09-11 18:22
Last Updated: 2017-11-15 21:56

Dependencies (9)

Required by (1000)

Sources (6)

Latest Comments

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

joschi commented on 2014-10-20 19:40

@Det Thanks to you. I mostly just copied the jdk PKGBUILD…

I think the line in the jdk7 PKGBUILD is correct (https://github.com/joschi/AUR/blob/e3bae70bc35a9776164bfd2697e3b327be6cfc08/jdk7/PKGBUILD#L125). If the license was linked as /usr/share/licenses/jdk it would lead to conflicts with the jdk PKGBUILD.

Det commented on 2014-10-20 11:42

Great work. However, the second license line should also say $_pkgname, not $pkgname:

ln -sf /usr/share/licenses/java$_major-$_pkgname/ "$pkgdir"/usr/share/licenses/$pkgname

disponiblekonto commented on 2014-10-16 08:25

I managed to update by:

$ pacman -Rdd jdk7
$ packer -S jdk7

wtribe commented on 2014-10-15 19:31

I third the comment. It depends on java-environment-common and java-runtime-common but then conflicts with files in them. Maybe something changed in the two common packages?

Or, am I missing something else?

madscience commented on 2014-10-15 12:19

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

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

Det commented on 2014-10-13 03:02

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

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

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

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.