aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorGreg Lewis <glewis@FreeBSD.org>2004-11-11 19:18:25 +0000
committerGreg Lewis <glewis@FreeBSD.org>2004-11-11 19:18:25 +0000
commit6ae9fe2889814998768362aa037a5fc66657d9d5 (patch)
treea8a990b736fddacfe8cad42a95a484659e41d4a9 /UPDATING
parent280df4e4cedc6b10cf8c1175ee494973c9160f98 (diff)
downloadports-6ae9fe2889814998768362aa037a5fc66657d9d5.tar.gz
ports-6ae9fe2889814998768362aa037a5fc66657d9d5.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING19
1 files changed, 19 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 306ad6ce2eb3..e2d322157a07 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,25 @@ You should get into the habit of checking this file for changes each
time you update your ports collection, before attempting any port
upgrades.
+20041111:
+ AFFECTS: users of java
+ AUTHOR: glewis@FreeBSD.org
+
+ javavmwrapper has been rewritten. It now creates symbolic links for
+ all executables of the Java VMs that have been registered with it.
+ These symbolic links may impact which version of Java you are using,
+ depending on your PATH, which may need to be adjusted.
+
+ For example, if your path is:
+
+ ${LOCALBASE}/bin:${LOCALBASE}/jdk1.4.2/bin
+
+ then previously "java" would resolve to ${LOCALBASE}/jdk1.4.2/bin/java.
+ With the new javavmwrapper it will resolve to ${LOCALBASE}/bin/java.
+ Depending upon the Java VMs that are registered and various environment
+ variables, it may or may not be ${LOCALBASE}/jdk1.4.2/bin/java that is
+ run by javavmwrapper via the symbolic link ${LOCALBASE}/bin/java.
+
20041107:
AFFECTS: users of x11/kdebase3
AUTHOR: kde@freebsd.org