[
https://issues.apache.org/jira/browse/IVYDE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252548#comment-13252548
]
Eric Milles commented on IVYDE-299:
-----------------------------------
That makes sense. My assumption was that everything was being done relative to
a project. But for launch configurations that is not the case. So to have the
classpath container work generically for projects and launches, IvyDE needs a
way to be directed to the necessary files without assuming any particular
project. So currently, the project is stated explicitly using the "project"
URL parameter.
Additionally, you are saying there is a variable ${ivyproject_loc} that could
be leveraged. But I'm not sure I understand exactly what directory to which it
is referring. In the case of launch configurations, would this variable be
useful?
> 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
