Package Base Details: java7-openjdk

Git Clone URL: https://aur.archlinux.org/java7-openjdk.git (read-only)
Keywords: infinality java jdk jre
Submitter: trollixx
Maintainer: trollixx
Last Packager: trollixx
Votes: 27
Popularity: 0.000022
First Submitted: 2014-07-22 00:55
Last Updated: 2018-04-13 22:32

Latest Comments

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

nanomad commented on 2014-10-16 07:46

Sure, here's a quick recap of what I did:

https://gist.github.com/nanomad/c013f6603984e5372eb3

trollixx commented on 2014-10-15 21:01

@nanomad, sounds interesting. Could you tell us more on how to use OBS? I could host a repo then.

nanomad commented on 2014-10-15 19:58

My bad sorry, somehow the index page was showing an old version. No idea why. Maybe work's proxy acting funny.

Btw, I managed to build and host binary packages for this and java8 using OpenSuse Build System. Let me know if you're interested in mantaining a binary repo.

trollixx commented on 2014-10-15 16:21

@chrbayer, yes, same with mine.

@nanomad, why have you flagged the package?

chrbayer commented on 2014-10-15 16:01

Mine was flagged out by nanomad an email told me...

chrbayer commented on 2014-10-15 15:59

This is strange... I flagged the package out of date before you have updated it, but not after... My 8u25 packages are flagged out of date, too...

trollixx commented on 2014-10-15 15:42

Why has the package been flagged out of date? I've just updated it, and I don't see any new versions in ABS released in the last 30 minutes.

trollixx commented on 2014-10-12 20:27

@galaux, thank you for the update. I'll update this package in the nearest days.

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-05 13:15

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.