ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Sinclair (JIRA)" <>
Subject [jira] Commented: (IVYDE-26) load issue in eclipse
Date Mon, 24 Nov 2008 22:31:44 GMT


Jeffrey Sinclair commented on IVYDE-26:

Nicolas, that's a fair comment and a good point. In our Ivy setup, the ivy-settings refer
to some default settings that are pulled in over the network. I'd rather have an option to
'reload settings' than incur a forced performance hit with Eclipse blocking on IO for the
use-case that the centralised settings are updated. Would it be possible to tie in this feature
into the 'resolve' and 'refresh' option for the IvyDE managed dependency container (ideally
on a per project basis and also with some global setting). For example a checkbox to say 're-load
settings on re-resolve and refresh'? This way it is still left up to the end user to incur
any potential slowness but if they are happy with it they are guaranteed to have the correct
settings when resolving or refreshing the container.

> load issue in eclipse
> ----------------------------------------
>                 Key: IVYDE-26
>                 URL:
>             Project: IvyDE
>          Issue Type: Improvement
>         Environment: Configured IvyDe. and ivy 1.3.1 Eclipse 3.2
>            Reporter: Michel Tiemens
>            Assignee: Xavier Hanin
>            Priority: Minor
>             Fix For:
> I have got IvyDe and Ivy working in a relatively small project.
> I use the folowing properties in my
>  - development.dir=/prive/development/ontw
>  - workspace.dir=/pslagdigi
> using them in:
>  - ivy.shared.default.root=/common-repository/shared
> I now noticed the issue that when I change the workspace.dir variable for instance IvyDe
tries to resolve the artifacts using my old workspace.dir value. It is after I restart my
workspace I get the correct behaviour. 
> It might be an improvement to have a refresh configuration option in the ivyde plugin's

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message