[jira] [Commented] (IVYDE-299) IvyDE is making .classpath file writable and rewriting it

["Sebastian Krause (JIRA)" <ji...@apache.org>]

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

Sebastian Krause commented on IVYDE-299:
----------------------------------------

*@Nicolas:* Unfortunately even with the ${ivyproject_loc} variable it seems impossible to leave the .classpath file in a VCS if you have the project checked out under different names. Let's say you have "myproject" checked out under the project name "myproject-dev" and a second project "myproject-stable" at a different revision. The classpath entry will look something like this:

bq. <classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/?project=myproject-stable&amp;ivyXmlPath=ivy.xml&amp;confs=*&amp;ivySettingsPath=%24%7Bivyproject_loc%7D%2Fivysettings.xml&amp;loadSettingsOnDemand=false&amp;propertyFiles="/>

Now in the other project IvyDE will always change the "project" parameter into "myproject-dev" and my VCS system will try to check it in. The only current solution so far it to simply let the VCS completely ignore the classpath file.
                
> 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