[
https://issues.apache.org/jira/browse/IVYDE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423099#comment-13423099
]
Martin Schaffoener commented on IVYDE-299:
------------------------------------------
So this issue won't be fixed... However, this is a major blocker for my company
upgrading from IvyDE2.1.0. We have had the .classpath files under VCS control
for years to share the correct settings with all developers in the company.
Even if only Eclipse is supposed to modify this file, I do not think this
mandates the .classpath file not being version controlled.
Even if we could make changes now to make the .classpath file work with
IvyDE2.1.0 in a way that an upgrade to 2.2.x would not rewrite it (which, it
appears, is not supported), we would still see the .classpath files altered
automatically when switching back to a historic changeset id. And this would
leave uncommitted changes in the workspace even though we're looking at an old
version - something which looks weird and is very hard to explain to a user.
Apparently IvyDE 2.2.x can read .classpath files with entries created by IvyDE
2.1.0. Why can't we just read the old settings, convert them into new internal
representations, but skip rewriting the .classpath file until one actually
makes a change to the IvyDE classpath containers?
Finally: What can or must I do to have this bug reopened and fixed?
> 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
