Summary: | dev-java/maven-bin uses generation-1 vm when running | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Darren Davison <darren> |
Component: | Current packages | Assignee: | Java team <java> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | f5d8fd51ed1e804c9e8d0357e8614e0493b06e96 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Darren Davison
2006-07-20 02:43:55 UTC
dammit, this may be a false report. JAVA_HOME is incorrectly set in my environment to the 1.4.12 system VM (or perhaps it's meant to be that way, I don't know) but the mvn shell scrip never executes java-config --jre-home because JAVA_HOME is already set. To workaround, I've now added export JAVA_HOME="" to my ~/.bashrc and maven behaves as expected. Apologies for not realising this sooner; I guess it's just a question of whether JAVA_HOME should be set that way by default or not. JAVA_HOME is used by generation 1 (old system) only - it's safe to unset it for users, but not for root (java-config-1 relies upon it). After migration is completed and java-config-1* is removed the problem will be gone. Until then it's quite hard to fix it. |