ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <j...@apache.org>
Subject [jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
Date Mon, 18 Feb 2008 10:12:36 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569836#action_12569836
] 

Nicolas Lalevée commented on IVYDE-70:
--------------------------------------

Bad news.
Whereas the configuration of an existing class path container works well with classpath attributes,
the creation doesn't. The JDT doesn't care about the classpath attributes given from the "ContainerPage".
Again I asked help (now at the right place) http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.tools.jdt/msg22184.html
But I got no good answer yet.

So finally I think that the configuration should be in the container path. I will try that.

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


Mime
View raw message