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 Tue, 19 Feb 2008 17:38:44 GMT


Nicolas Lalevée updated IVYDE-70:

    Attachment: IVYDE-70.patch

Here is a patch.

* the two configuration panes merged
* the configuration pane has a global "project specific settings" check box
* now we can only finish the configuration panes if it is correctly configured (some disabled
finish button)

A little about the implementation:
* the container configuration is defined in the container path. The paths (ivysettings, ivy.xml
paths) are URL encoded
* the configuration that was managed in the IvyPlugin is now handled in two new beans: the
global configuration and the container one. The code is now simpler.

I have tested with some tiny projects, it works fine. But due to the big change, the patch
should be also tested with bigger project, and also with project having default ivysettings.

> 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.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