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 Fri, 18 Jan 2008 16:02:35 GMT


Xavier Hanin commented on IVYDE-70:

Thanks for your investigation Nicolas, you've found the exact problem, but it seems it won't
be easy to solve in IvyDE. According to the bug in eclipse marked as won't fix, we can't have
the information when the project is opened that some project preferences are available. This
comes only later... if some project preferences are available, but we can't be sure. So what
can we do? Delay dependency resolution? Make the resolution on demand only? this will affect
all startups, not only when you import... so we have to be careful with what we do. But maybe
making the resolution on demand only is the best solution. Indeed, this can take a lot of
time, and sometimes people complain when starting eclipse with IvyDE installed that it takes
a very long time, or even hang. So on startup or project import we could fetch the classpath
container only if a dependency resolution report is available in cache, and keep it empty
if we have no inormation. Then users would have to launch a resolve manually in such case.
Since this can be a long operation, I don't think it's that silly to do things like this.


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