created by pkg(8) during upgrades
It happens because the deinstall script tries to clean up the potential manual
VM registration by cleaning out all symlinks to bin/javavm
Given all VM are registring/unregistering themselves this part is not needed
The other thing the script was doing handling the configuration which has been
replaced by @sample.
pkg-install has been modified to drop the handling of the configuration file but
keep the auto registration if all VM found. While this part is not necessary as
well, we keep it because otherwise anyone doing delete/install on javavmwapper
version 2.5 being the installed version would end up with all VM unregistered.
The pkg-install should be removed after EOL of FreeBSD 10.3
PR: 210313
MFH: 2016Q3
. Remove support for diablo* and j* ports.
. Add support for linux-oracle* ports.
. Remove support for Java version 1.5.
. Add support for Java version 1.8.
. Add support for Oracle as a vendor.
. Bump PORTVERSION.
. Remove CONFLICTS for ports that no longer exist.
- Make sure to destroy all symlinks pointing to ${PREFIX}/bin/javavm and
${PREFIX}/etc/javavms when we deinstall the package.
Reviewed by: glewis (maintainer)
Feature safe: yes
E.g. for jdk1.6.0 and openjdk6 will use '6' as the version.
. Modify the preference order for Java VMs used by the internal fallback
logic to reflect that openjdk is now the default Java VM rather than diablo.
. Remove code for Java vendors that are no longer in the ports tree (e.g.
blackdown, ibm).
. Remove code for handling version numbers that are no longer present in
the tree (e.g. only 1.5 and up is supported).
. Note that openjdk is a native Java VM.
. If the environment variable JAVAVM_FALLBACK_ONLY is set then only use the
internal logic to select a Java VM, don't use the ports logic even if the
ports collection is installed. [1]
. Update the manual page for JAVAVM_FALLBACK_ONLY.
. Bump version to 2.4.
PR: 167799 [1]
remove support for them from bsd.java.mk. As Jikes is not available in Java 1.5
or higher, remove it from bsd.java.mk too (suggested by hq@) and from the ports
which used it (only occurences were USE_JIKES=no). Support for the Blackdown VM
is also removed, as it is not available in Java 1.5 and higher.
Also remove the mapping from Java 1.1-1.4 to Java 1.5+ in bsd.java.mk to detect
old, broken ports; therefore bump the minimal value of JAVA_VERSION to 1.5.
While here, replace static values of JAVA_VERSION in files/*.in by
%%JAVA_VERSION%% .
PR: ports/158969
Submitted by: rene
Tested on: pointyhat-west -exp
. Note such support in the manual pages.
. Correctly determine the Java version of the OpenJDK ports when bsd.java.mk
isn't present.
. Bump version to 2.3.4.
pages if LANG is set to ja_JP.eucJP and the port is installed.
Diablo packages contain japanese manual pages and jman seems to format them
mostly fine.
Reviewed by: glewis (maintainer)
not invoke any Java programmes, but will instead print out what it would
have invoked and some related settings.
This work was inspired by the PR, but doesn't use its implementation.
PR: 96050
flags when being used to bootstrap the jdk15 port, and this was confirmed
by somebody else. However, javac doesn't seem to be happy with it so
turn it back off.
Submitted by: hq
causing problems for programmes such as jar(1). I actually believe it is
needed by some of the other programmes, but we'll add it as needed.
. Bump PORTREVISION for this change.
PR: 98586
Submitted by: Achilleas Mantzios <achill@matrix.gatewaynet.com>
before attempting to sort it when running checkvms. This prevents a
double error message for an unprivileged user.
. When asked to register a VM that is already registered, don't error.
Print a warning that the VM is already registered and don't add it to
the configuration file (but do check its links and sort the config
file still). This prevents problems with
'make install -DFORCE_PKG_REGISTER'
erroring out during the post-install stage for the JDK ports.
Bump PORTREVISION for this change since it affects the various JDK
ports. [2]
Reported by: anholt, via hq [2]
done separately).
. Much more stringent checks on VMs that we are trying to register. This
prevents most bogus and circular registrations. [1]
Suggested by: Josh Elsasser <josh@elsasser.org> [1]
utilities. Unfortunately this overrides any PATH that may have been
set by the user and hence affects the ability of java to execute
external programmes. So, save the PATH before setting it and then
restore it immediately before executing java.
. Bump PORTREVISION for this fix.
Reported by: Christian Laursen <xi@borderworlds.dk>
allow the simple use of multiple VMs. Brief detail of the main changes:
. When a VM is registered, symbolic links for its executables are
created in ${LOCALBASE}/bin. This allows people to just type
'java', 'javac', etc. without having to add the VM installation
directory to their PATH.
. The actual 'java' that is executed via one of these symlinks is
determined by the order of the (sorted) configuration file
${LOCALBASE}/etc/javavms and by the environment variables
JAVA_VERSION, JAVA_OS and JAVA_VENDOR which function to select
a VM as they do in the ports framework.
. There is a new command, checkvms, to sanity check the configuration
and symlinks.
. The "javavm" executable is currently retained in its original capacity
as a synonym for Java for backward compatibility. However, its use
is deprecated.
. Temporarily set MAINTAINER to myself to make monitoring any initial
bug reports easier. The intent is to convert it to java@ at a later
date.
This is built on the ideas of znerd, hq and Shelton C. Johnson Jr., with
hq and Shelton contributing code and reviews.
PR: 27079, 39080
Reviewed by: hq, Shelton C. Johnson Jr. <shelton_c_j@yahoo.com>
