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 Sat, 19 Jan 2008 12:36:37 GMT

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

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

I have some colleagues which playing with Eclipse is their job. I have ask them, they never
faced that issue, but they had some ideas: for instance we can try to use the scheduling rules
so that the open operation and the refresh job will block the resolve job. It am still unsuccessful,
but I have not gone deeply into that solution yet.

If that solution doesn't work, I thought of storing data even if the user didn't defined preferences.
The data stored would simply be a no-configuration tag. So we should always try to load the
preferences. And if the preferences are not there, then we wait for them to be loaded in being
a preference listener.
I prefer this solution because there will be less input request from the user. And as the
job is now asynchronously launched, the eclipse won't freeze.

But if that last solution doesn't work either, then your solution is the best yes.



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