Bug 105553 - Exception while retrieving /PROJECT/.classpath, will mark classpath as invalid
Summary: Exception while retrieving /PROJECT/.classpath, will mark classpath as invalid
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 RC4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-29 01:40 EDT by Jose Nicolas Castellano CLA
Modified: 2007-06-20 04:57 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Nicolas Castellano CLA 2005-07-29 01:40:52 EDT 
The project cannot find exactly the classpath, replys with error Exception while
retrieving /PROJECT/.classpath, will mark classpath as invalid, this is the
output log:

!ENTRY org.eclipse.core.runtime 2 2 2005-07-29 07:26:16.878
!MESSAGE Job found still running after platform shutdown.  Jobs should be
canceled by the plugin that scheduled them during shutdown:
org.eclipse.update.internal.scheduler.AutomaticUpdateJob
!SESSION 2005-07-29 07:26:18.10 ------------------------------------------------
eclipse.buildId=I20050627-1435
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.jdt.core 4 4 2005-07-29 07:26:26.472
!MESSAGE Exception while retrieving /PROJECT/.classpath, will mark classpath as
invalid
!STACK 0Exception while retrieving /PROJECT/.classpath, will mark classpath as
invalid
java.io.IOException: Bad format
	at org.eclipse.jdt.internal.core.JavaProject.decodeClasspath(JavaProject.java:812)
	at
org.eclipse.jdt.internal.core.JavaProject.readClasspathFile(JavaProject.java:2551)
	at org.eclipse.jdt.internal.core.JavaProject.getRawClasspath(JavaProject.java:1845)
	at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1948)
	at
org.eclipse.jdt.internal.core.search.JavaSearchScope.add(JavaSearchScope.java:108)
	at
org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.initialize(JavaWorkspaceScope.java:84)
	at
org.eclipse.jdt.internal.core.search.JavaSearchScope.<init>(JavaSearchScope.java:62)
	at
org.eclipse.jdt.internal.core.search.JavaSearchScope.<init>(JavaSearchScope.java:58)
	at
org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.<init>(JavaWorkspaceScope.java:29)
	at
org.eclipse.jdt.internal.core.JavaModelManager.getWorkspaceScope(JavaModelManager.java:1421)
	at
org.eclipse.jdt.internal.core.search.BasicSearchEngine.createWorkspaceScope(BasicSearchEngine.java:157)
	at
org.eclipse.jdt.core.search.SearchEngine.createWorkspaceScope(SearchEngine.java:392)
	at org.eclipse.jdt.core.JavaCore$1.run(JavaCore.java:2623)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
Comment 1 Olivier Thomann CLA 2005-07-29 11:39:24 EDT 
Could you please provide a test case?
Comment 2 Jose Nicolas Castellano CLA 2005-08-01 10:33:51 EDT 
I import an existing CVS project(it's a big project), putting in my .cvsignore,
.classpath file.
Then, the contents of the .classpath:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" path=""/>
	<classpathentry exported="true" kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
	
	<classpathentry kind="output" path=""/>
</classpath>

Simple no? It's very rarely, also fails with the same bug in version 3.0
Comment 3 Olivier Thomann CLA 2006-10-10 11:28:13 EDT 
Build path issue.
Comment 4 Frederic Fusier CLA 2007-06-19 13:28:16 EDT 
Cannot reproduce using 3.3 RC4