Wolfgang Liebich wrote:
Hi,
I have a gentoo system with many parallel JDKs installed. java-config -L
says
[ibm-jdk-1.3.1] IBM JDK 1.3.1 (/etc/env.d/java/20ibm-jdk-1.3.1)
[sun-jdk-1.5.0.06] Sun JDK 1.5.0.06 (/etc/env.d/java/20sun-jdk-1.5.0.06)
[ibm-jdk-1.4.1] IBM JDK 1.4.1 (/etc/env.d/java/20ibm-jdk-1.4.1)
[sun-jdk-1.3.1.16] Sun JDK 1.3.1.16 (/etc/env.d/java/20sun-jdk-1.3.1.16) *
[sun-jdk-1.4.2.09] Sun JDK 1.4.2.09 (/etc/env.d/java/20sun-jdk-1.4.2.09)
[blackdown-jdk-1.4.2.02] Blackdown JDK 1.4.2.02
(/etc/env.d/java/20blackdown-jdk-1.4.2.02)
This is mainly b/c I want to use this box for Java compatibility
evaluation. My main (default) JDK for now is sun-jdk-1.3.1.16. BUT when
I try to update dev-java/xml-commons, the JDK 1.5 patch is applied
ALWAYS - it ignores the system JDK to be used. SO it seems that in order
to update this package I have to switch to a 1.5 JDK - is this right? It
doesn't seem so to me...
Puzzled,
Wolfgang
It is, check the
/usr/portage/dev-java/xml-commons/files/1.0_beta2-jdk15.patch and you
will see that it just changes the source and target attributes in the
build.xml file. The patch is not dependent on the system jdk used. In
general we try to prefer noncondional patches because it makes debugging
problems easier. Please also note that there is a gentoo-java mailing
lists where java related questions are likely to get better answers than
on gentoo-users.
You should also note that most ebuilds depend on =virtual/jre-1.4 so
having 1.3 as the system jdk to emerge stuff might not work.
Regards,
Petteri
signature.asc
Description: OpenPGP digital signature
