[
https://issues.apache.org/jira/browse/IVYDE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252451#comment-13252451
]
Peter Vestman commented on IVYDE-299:
-------------------------------------
We are also suffering from this issue. The problem we are having is that we do
not want the name of the project directory in the .classpath because we have
multiple versions of the same project checkedout under different names.
IvyDE adds the directory name in .classpath as project=MyProjectRelease4.0 and
also for the ivysetting path. for the ivysettings path we used to be able to
write project:///ivysettings.xml but this is now rewritten to
workspace_loc:/projectname. IvyDE used to be able to know in with project it
was operating without the project parameter. No other eclipse plugins insist on
modifying the .classpath to be dependent on the directory name.
This is related to IVYDE-254
> 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
