ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Milles (Commented) (JIRA)" <>
Subject [jira] [Commented] (IVYDE-299) IvyDE is making .classpath file writable and rewriting it
Date Thu, 12 Apr 2012 15:25:24 GMT


Eric Milles commented on IVYDE-299:

If I find that Ivy is making a change to the IvyDE line, make that change and find that IvyDE
is still rewriting the file continuously, would you consider a fix?  I do understand that
the .classpath file is an Eclipse-managed entity.  But, up to this point, we were able to
make our own annotations to the .classpath file that would stick as long as we weren't making
any changes to the build path of the project.

Regardless of that, it is still important that we not have a pending change on .classpath
for every developer.  This is very dangerous and often leads to unintended changes to the
Java build path ending up committed to source control.
> IvyDE is making .classpath file writable and rewriting it
> ---------------------------------------------------------
>                 Key: IVYDE-299
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message