Bug 37338 - eclipse denies write on .classpath file when invalid classpath in .classpath file.
Summary: eclipse denies write on .classpath file when invalid classpath in .classpath ...
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
: 37356 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-05-07 13:43 EDT by JJ CLA
Modified: 2009-08-30 02:05 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JJ CLA 2003-05-07 13:43:24 EDT
Bascially I have a eclipse 1.x project that I imported.  Inside that .classpath
file are these lines:

    <classpathentry kind="lib" path="classes"/>
    <classpathentry kind="src" path="source"/>
    <classpathentry kind="output" path="classes"/>

when I try to compile I get:

Invalid classpath in 'uportal16-vista/.classpath' file: Source folder
'uportal16-vista/source' cannot output to library 'uportal16-vista/classes'.

The project was not built due to classpath errors (incomplete or involved in cycle).

Now when I try and remove the erroronous
<classpathentry kind="lib" path="classes"/> manually from the .classpath file in
eclipse when I try to save I get:

"Save could not be completed.  Reason: Could not write file:
e:\project-name\.classpath.

Now if I go outside of eclipse use a text editor and remove the line all the
while eclipse is still open I can save the file fine.  I then refresh in eclipse
and the project compiles.
Comment 1 Philipe Mulet CLA 2003-05-12 06:25:34 EDT
We should tolerate this scenario. If unable to read in the old CP, we could 
treat it as empty.
Comment 2 Jerome Lanneluc CLA 2003-07-10 11:07:39 EDT
I cannot reproduce in 2.1. In the latest build, we accept this scenario again, 
so it doesn't happen either.

What build were you using when this happened?
Comment 3 JJ CLA 2003-07-14 13:26:56 EDT
I was using the lastest milestone as of the date I logged the bug.  I am pretty
sure that was 2.1 final
Comment 4 Jerome Lanneluc CLA 2003-07-15 06:50:55 EDT
Can you reproduce the problem?
Comment 5 Philipe Mulet CLA 2003-07-21 12:25:59 EDT
*** Bug 37356 has been marked as a duplicate of this bug. ***
Comment 6 Jerome Lanneluc CLA 2003-08-21 11:54:32 EDT
Please reopen if you can reproduce the problem.
Comment 7 Philipe Mulet CLA 2004-04-08 09:32:25 EDT
Timed out
Comment 8 Denis Roy CLA 2009-08-30 02:05:19 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.