ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Schaffoener (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IVYDE-299) IvyDE is making .classpath file writable and rewriting it
Date Thu, 26 Jul 2012 17:21:38 GMT

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

Martin Schaffoener commented on IVYDE-299:
------------------------------------------

Couldn't we make this a global configuration option to not update the .classpath files, so
that we can start Eclipse, set the option, revert .classpath files? Or have it configurable
via a JVM system property? Or put it into the .project file before upgrading? (BTW: I think
I noticed the .project also getting touched by the upgrade?)
                
> 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

        

Mime
View raw message