[ https://issues.apache.org/jira/browse/IVYDE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-299.
-----------------------------------
Resolution: Fixed
Fix Version/s: trunk
Assignee: Nicolas Lalevée
Ironically, this .classpath upgrade was producing some mess in the classpath container initialization.
In some use case the classpath container didn't even get initialized and we could see the
container path in place of the name of the container (ivy.xml[*]). I didn't saw it until recently,
maybe related to my recent move to Eclipse 4.
So I removed that .classpath 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: Improvement
> Affects Versions: 2.2.0.beta1
> Reporter: Eric Milles
> Assignee: Nicolas Lalevée
> Fix For: trunk
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
|