ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
Date Fri, 08 Feb 2008 16:51:07 GMT


Nicolas Lalevée commented on IVYDE-70:

It works !!! :)
Effectively this is the solution, we will have something like extra entries in the .classpath
        <classpathentry kind="con" path="org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/ivy.xml/*">
                        <attribute name="ivySettingsPath" value="file:/home/nicolasl/dev/......../tools/1.0/ivyconf-eclipse.xml"/>

The patch is not ready, as I have some trouble while trying to change the Ivy's configuration
the project being opened. But I will make it work!

I have another request about the UI. The pages being merged, there will be in fact two tabs,
the main one (ivy.xml + confs) and the advanced one (ivyseetings.xml + extensions). In the
advanced one I would like to present it as the other Eclipse classic configurations, with
a global "Enable project specific settings" and a link to the global conf (See the "Java code
style" configuration page), more than having a per-config entry inheritance. We would loose
a little bit of the fine-graininess of the configuration, but I think this will be a lot better
user friendly.

> The project ivy configuration is not taken into account on the first run
> ------------------------------------------------------------------------
>                 Key: IVYDE-70
>                 URL:
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>         Environment: Eclipse 3.2
>            Reporter: Nicolas Lalevée
>         Attachments: IVYDE-70-preferenceListenerTry.patch
> Starting with an empty workspace, I import a project which already have its Ivy preferences
> After the import the classpath is made of some ibiblio jars, whereas I was expecting
the ones from my internal repository. After a resolve, the classpath has the proper jars,
from my internal repository.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message