ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Commented: (IVYDE-70) The project ivy configuration is not taken into account on the first run
Date Tue, 19 Feb 2008 17:22:43 GMT


Xavier Hanin commented on IVYDE-70:

That sound nice, I guess you'll be able to commit it yourself :-)

About the information encoding, I know we shouldn't actually read the .classpath, but I think
it's not easy to understand the encoding you choose. Maybe we could use something more standard,
like the URI query part with parameters encoded with application/x-www-form-urlencoded MIME
format, for which we already have the URLEncoder and URLDecoder in the JRE (which seems to
be what you already use. Then the path would look pretty much like an URI, except for the
beginning (no protocol, ...). Something like:

Unless this is not something possible with eclipse classpath parsing?

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