You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2008/03/04 11:56:40 UTC
[jira] Updated: (IVYDE-70) The project ivy configuration is not
taken into account on the first run
[ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée updated IVYDE-70:
---------------------------------
Attachment: IVYDE-70-urlish-r633421.patch
New patch that fix a bug introduced in the path: the ivy instance was attached to the container and was not changing even if the ivySetting path change. So reconfiguring the container to be project-specific or not-project-specific was not working properly.
> The project ivy configuration is not taken into account on the first run
> ------------------------------------------------------------------------
>
> Key: IVYDE-70
> URL: https://issues.apache.org/jira/browse/IVYDE-70
> 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-r629775.patch, IVYDE-70-urlish-r633421.patch, IVYDE-70-urlish.patch, IVYDE-70.patch
>
>
> Starting with an empty workspace, I import a project which already have its Ivy preferences configured.
> 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.