[
https://issues.apache.org/jira/browse/IVYDE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423122#comment-13423122
]
Nicolas Lalevée commented on IVYDE-299:
---------------------------------------
I am sorry this is making some mess in your project Martin, but I feel quite
uncomfortable not forcing the .classpath to be upgraded.
Now I remember why the project name was added to the IvyDE classpath entry. For
some reason, in the launch configuration, if a project is added manually to the
source lookup and it contains an IvyDE classpath container, the project
reference is lost by the JDT. So I had to add it to the IvyDE container. So now
if the .classpath is not upgraded, we may introduce a bug I had a hard time to
fix.
We could think of an option saying "do not upgrade .classpath, I know what I am
doing". But to be able to check this option, you will have to upgrade first...
I cannot find a good solution to your issue.
> IvyDE is making .classpath file writable and rewriting it
> ---------------------------------------------------------
>
> Key: IVYDE-299
> URL: https://issues.apache.org/jira/browse/IVYDE-299
> Project: IvyDE
> Issue Type: Bug
> Affects Versions: 2.2.0.beta1
> Reporter: Eric Milles
> Attachments: classpath.txt
>
>
> The latest beta (2.2.0b1) is continually rewriting the project's .classpath
> file. This is problematic for two reasons: 1) Our project is submitted to
> source control, so the rewriting causes a pending change for the .classpath
> file and 2) We are manually editing the .classpath file to add useful
> comments, which are being lost when the file is written again. Reverting to
> 2.1.0 and the issue goes away.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
