You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Matt Benson <gu...@yahoo.com> on 2009/03/24 20:17:11 UTC
[ivyde] WorkspaceResolver
Nicolas (or anybody, but practically, Nicolas):
I am trying to use the WorkspaceResolver in IvyDE 2.0.0beta1 to resolve project dependencies in Eclipse where the dependency is not found any any repo (yet, anyway). I have selected "Resolve dependencies in workspace" in the global Ivy settings, as well as the project Ivy settings, yet I still see nothing in the log that would indicate the workspace resolver is being called into play. I have NOT exported the Ivy library in the Java Build Path/Order and Export tab for my dependency project; it seems that doing so would not require any special work on the part of the IvyDE plugin, so I would think that I am not supposed to do that. How can I know whether the workspace resolver is being used, and if not, why not? :)
Thanks,
Matt
Re: [ivyde] WorkspaceResolver
Posted by Kirby Files <kf...@masergy.com>.
Nicolas Lalevée wrote on 03/25/2009 11:29 AM:
> The worksapce resolver implemented in the beta1 is a sort of workaround. The
> process implemented is to launch a normal resolve. Then if some of the
> resolved dependency is mathing the organization name and module name of some
> project in your Eclipse workspace, then IvyDE will switch the resolved jar by
> the Eclipse project.
> So if you don't have any build of your dependency, it cannot work because the
> first normal resolve will fail.
Even with that limitation, I'm excited by the new feature. It's very
nice to have changes in my project dependencies reflected immediately.
Some downsides: it causes a resolve of every project in the workspace,
which can be quite slow at times. I'm getting much more careful about
closing projects which I don't need for my current work. It also makes
figuring out the cause of the "X" error icon on a project a little
trickier, as it can now indicate a problem in a dependency. The
Problems View is getting much more use.
Thanks for implementing that. Once we also have a plugin for ant
classpath contribution of ivy, the integration into Eclipse will be
very nice.
Thanks,
--kirby
Re: [ivyde] WorkspaceResolver
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On mardi 24 mars 2009 20:17:11 Matt Benson wrote:
> Nicolas (or anybody, but practically, Nicolas):
>
> I am trying to use the WorkspaceResolver in IvyDE 2.0.0beta1 to resolve
> project dependencies in Eclipse where the dependency is not found any any
> repo (yet, anyway). I have selected "Resolve dependencies in workspace" in
> the global Ivy settings, as well as the project Ivy settings, yet I still
> see nothing in the log that would indicate the workspace resolver is being
> called into play. I have NOT exported the Ivy library in the Java Build
> Path/Order and Export tab for my dependency project; it seems that doing so
> would not require any special work on the part of the IvyDE plugin, so I
> would think that I am not supposed to do that. How can I know whether the
> workspace resolver is being used, and if not, why not? :)
The worksapce resolver implemented in the beta1 is a sort of workaround. The
process implemented is to launch a normal resolve. Then if some of the
resolved dependency is mathing the organization name and module name of some
project in your Eclipse workspace, then IvyDE will switch the resolved jar by
the Eclipse project.
So if you don't have any build of your dependency, it cannot work because the
first normal resolve will fail.
A more proper workspace resolver that will effectivelly consider the Eclipse
workspace as an Ivy repository has been implemented in the trunk of IvyDE. So
it will be able to resolve your project in Eclipse correctly.
Nicolas