[
https://issues.apache.org/jira/browse/IVYDE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-299.
-----------------------------------
Resolution: Won't Fix
I dont think we'll fix it. The .classpath is first meant to be manipulated by
Eclipse and its plugins, not people.
Your current .classpath has an entry about IvyDE. IvyDE 2.2 detects that it has
missing information, because it was generated by an IvyDE 2.1. So it updates it.
Maybe something that would work for you is to let first IvyDE change the
.classpath. Then replace it with your own version but keeping the one line
about IvyDE container. So IvyDE won't try to update it.
> 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
