ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (Commented) (JIRA) <>
Subject [jira] [Commented] (IVYDE-299) IvyDE is making .classpath file writable and rewriting it
Date Thu, 12 Apr 2012 16:21:17 GMT


Nicolas Lalevée commented on IVYDE-299:

@Peter: actually there is an undocumented variable, ivyproject_loc which should do the job
properly. Try setting ${ivyproject_loc}/ivysettings.xml

@Eric: the upward compatibility is not garanteed, and I think actually changing form 2.2 to
2.1 won't work properly.

Then I think you're looking for the variable ivyproject_loc I just wrote about. Eclipse doesn't
have such variable, IvyDE has a sort of hack for that, it does live in replace of the string
"${ivyproject_loc}". This is because the variable manager of Eclipse doesn't work relatively
to a project, it is global, unlike a classpath container like IvyDE's one.

And about the project name in the url, IIRC it was introduced to make IvyDE work properly
in launch configurations. It is possible to setup standalone IvyDE classpath container in
a launch configuration, and a launch configuration is is not particularly related to a project
(at least that's what the Eclipse API infer). Maybe this can be improved, but I had quite
some pain to make IvyDE work correctly in a launch configuration, so I won't rush into modifying
it. (and needless to say, patches are always welcomed :) ).

> 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