[ https://issues.apache.org/jira/browse/IVYDE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252508#comment-13252508 ] 

Eric Milles commented on IVYDE-299:
-----------------------------------

It appears that Ivy rewrote the URL parameters of the IvyDE classpath container from:

ivyXmlPath=ivy.xml&confs=local,master&ivySettingsPath=%24%7Bworkspace_loc%3AProjectName%2Fivysettings.xml%7D&loadSettingsOnDemand=false&propertyFiles=

to:

project=ProjectName&ivyXmlPath=ivy.xml&confs=local%2Cmaster&ivySettingsPath=%24%7Bworkspace_loc%3AProjectName%2Fivysettings.xml%7D&loadSettingsOnDemand=false&propertyFiles=

After this, it does not seem to be making any changes.  I am even able to alter the workspace_loc path to the settings file to a project_loc style "ivySettingsPath=%24%7Bproject_loc%7D%2Fivysettings.xml" (which was not working in IvyDE 2.1).

My question now is this: Are these new URL parameters compatible with IvyDE 2.1?  That is, could I safely make these changes and commit the to source control and have some developers with IvyDE 2.1 and some testing IvyDE 2.2b1 with the same .classpath?
                
> 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