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

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

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

About the container path. For Eclipse, it is a IPath. So as far as I understand, it is a path
as in a URL. So it could be possible to implement what you suggest.
In fact here is the scheme I implemented :
org.apache.ivyde.eclipse.cpcontainer.IVYDE_CONTAINER/ivy.xml/conf/ivysetting.xml/acceptedTypes/sourceTypes/javadocTypes/sourceSuffixes/javadocSuffixes/doRetrieve/retreivePattern/order
knowing that the ivy.xml, ivysettings.xml and the retrieve pattern are URL encoded. Hum..
and in fact I just realized that it should be the case for every configuration entry, the
user can broke its config in putting a / in its "javadocTypes" for instance. So it won't be
that different from what you suggested. It will be quite easy to write the serializer, but
the parser might be more complicated. I need to check the query string spec.

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