ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Updated: (IVYDE-70) The project ivy configuration is not taken into account on the first run
Date Thu, 21 Feb 2008 10:29:20 GMT


Nicolas Lalevée updated IVYDE-70:

    Attachment: IVYDE-70-urlish-r629733.patch

Updated path which fix some introduced bugs:
* if there were no the project specific conf, the global one was not taken into account
* in the container page, if there is no the project specific conf, the grayed values are now
the global configuration ones
* add some panaoïd check at the .classpath loading. Raising some Exception during to load
of the .classpath is making Eclipse completely lost.
* container resolve job was not triggered on global configuration change
* add a configuration entry for the alphabetical order in the global Ivy config

> 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, IVYDE-70-urlish-r629733.patch,
IVYDE-70-urlish.patch, IVYDE-70.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