Bug 251363

Summary: Cannot create a Java project with IBM JRE 5.0
Product: [Eclipse Project] JDT Reporter: Prakash Rangaraj <prakash>
Component: CoreAssignee: Jerome Lanneluc <jerome_lanneluc>
Status: VERIFIED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: Olivier_Thomann, pwebster
Version: 3.5   
Target Milestone: 3.5 M3   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Prakash Rangaraj CLA 2008-10-20 06:02:19 EDT
Build ID:  I20081016-1126

Steps To Reproduce:
1. Set IBM's 5.0 JRE as default and run the latest I-Build
2. Try to create a Java Project
3. You will get an error saying: '' is an invalid name on this platform.

No stack traces are found.

More information:
The ClasspathEntry.resolvedChainedLibraries() method tries to read the Manifest and if the ClassPath attribute is empty (as in the case of ibmcfw.jar), it creates a classpath which ends with an newline. Eventually when the folders are created for this path, it tries to create a folder for each segment and it fails in creating the '\r' folder. The error:

eclipse.buildId=I20081016-1126
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20070201 (JIT enabled)
J9VM - 20070131_11312_lHdSMR
JIT  - 20070109_1805ifx1_r8
GC   - 200701_09
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.sdk.ide
Command-line arguments:  -product org.eclipse.sdk.ide -data C:\Eclipse\workspace/../runtime-EclipseApplication -dev file:C:/Eclipse/workspace/.metadata/.plugins/org.eclipse.pde.core/Eclipse Application/dev.properties -os win32 -ws win32 -arch x86

Error
Mon Oct 20 15:27:05 IST 2008
'' is an invalid name on this platform.


Workaround: 
    Use a different JRE. (I tried the one bundled with Sun's 1.6 JDK)
Comment 1 Prakash Rangaraj CLA 2008-10-20 06:39:20 EDT
Adding Paul to the CC list
Comment 2 Jerome Lanneluc CLA 2008-10-20 07:07:13 EDT

*** This bug has been marked as a duplicate of bug 251079 ***
Comment 3 Olivier Thomann CLA 2008-10-27 16:34:11 EDT
Verified for 3.5M3 using I20081026-2000.
See bug 252264 for warnings in the .log file.