First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 13719
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Java team <java@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: cmickel@hotmail.com
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 13719 depends on: Show dependency tree
Bug 13719 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-01-11 09:41 0000
I'm doing some development in java using the 'jdom' class package. I installed  
it using portage, and added it to my user classpath using java-config 
--set-user-classpath.  
The problem is that I am using sun java 1.4.1 and java-config added the jdom 
version for java 1.1 to the classpath first, and the 'real' jdom for newer 
versions of java later. It also added the sun.java.collections classes to the  
classpath, even though these are included in newer versions of the jdk in the  
java.util.*; classes. I fixed the problem (after a couple of hours of  
debugging code that I was 'positive' should work) by deleting the  
jdom-jdk11.jar file and collections.jar from the ~/.gentoo/java-env-classpath 
and now everything works ok. I'm not sure if this is a problem with the jdom 
package (I rebuit it manually using ant and it didn't build the uneeded jar 
files) or java-config. I guess either one could be changed to fix it.

------- Comment #1 From Matthew Kennedy (RETIRED) 2003-01-12 12:52:20 0000 -------
fixed

First Last Prev Next    No search results available      Search page      Enter new bug