Summary: | java-config leaves .gentoo/java-env which does not reference .gentoo/java | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Allen S. Rout <asr> |
Component: | Current packages | Assignee: | Java team <java> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | aether |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 31468 |
Description
Allen S. Rout
2004-04-13 09:45:23 UTC
Fix is in CVS, new java-config release in a few days. Fixed in 1.2.7 . I am using 1.2.10 and this bug is not fixed. The following are 2 scenarios that is happening if starting from scratch: Scenario 1: 1) User wants to use system vm so don't set user vm. 2) User sets his user classpath to include commons-logging. Result -> java-config creates .gentoo/java-env-classpath -> java-config creates .gentoo/java-env Contents of java-config sources .gentoo/java. Summary: The classpath never get sourced. Scenario 2: 1) User sets own vm. Result -> java-config creates .gentoo/java-env -> java-config creates .gentoo/java -> java-config creates source scripts for csh. 2) User sets commons-logging in his user path. Result -> java-config creates .gentoo/java-env-classpath Contents of java-config sources .gentoo/java Summary: Seeing that both .gentoo/java and .gentoo/java-env contain a reference to java-env-classpath, the classpath do not get set. Solution: Source java-env-classpath from java-env. Typo: For scenario 1 it is the contents of java-env which sources and not java-config. setting a user and system classpath though java-config will be deprecated in the next version if you want todo this put something like: export CLASSPATH="${CLASSPATH}:$(java-config -p pkg1,pkh2)" in your .profile (if using bash) |