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 Philipp Wetzler <ph...@colorado.edu> on 2009/12/17 19:48:50 UTC
IvyDE workspace resolution with Maven projects
Hello,
now that my dependency resolution works on the command line, I'm
encountering a problem with IvyDE, and I'm not sure if this is the expected
behavior. My Ivy-managed Eclipse project depends on other projects that are
managed by Maven. Some of those projects I also have open as projects in
Eclipse; the org, name and revision match exactly.
I enabled "resolve dependencies in workspace" for the project in the
properties of the ivy.xml classpath container, but that seems to have no
effect. I'm not sure where I'd look for a trace of the workspace resolver's
activities, but there's nothing in the log files, and the respective
dependencies are resolved in the normal, download-the-artifact way.
An obvious explanation would be if the workspace resolver doesn't work on
Maven projects -- nothing in the docs seems to confirm or deny that.
Alternatively, I misconfigured something, in which case: how do I go about
debugging my configuration of IvyDE?
thanks
Philipp
Re: IvyDE workspace resolution with Maven projects
Posted by Philipp Wetzler <ph...@gmail.com>.
Nicolas,
thanks, that explains it, then. My Maven projects are managed using one of
the Maven Eclipse plugins (I didn't even know IvyDE could be used in that
way). I guess I'll experiment a bit with IvyDE containers on those projects,
but more likely I'll end up managing the inter-project dependencies myself.
Thanks!
Philipp
2009/12/19 Nicolas Lalevée <ni...@hibnet.org>
> Does your maven project is managed by the M2Eclipse plugin or IvyDE ?
> The workspace resolver will only work on projects that are managed by
> IvyDE. More precisely, it will search for every Java project which has an
> IvyDE dependency container configured. For instance it could work with an
> M2Eclipse project which have also the Java nature, and in which there is a
> IvyDE container; but this probably would make a classpath hell...
>
> Nicolas
>
>
Re: IvyDE workspace resolution with Maven projects
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On Thu, 17 Dec 2009 11:48:50 -0700, Philipp Wetzler
<ph...@colorado.edu> wrote:
> Hello,
>
> now that my dependency resolution works on the command line, I'm
> encountering a problem with IvyDE, and I'm not sure if this is the
expected
> behavior. My Ivy-managed Eclipse project depends on other projects that
are
> managed by Maven. Some of those projects I also have open as projects in
> Eclipse; the org, name and revision match exactly.
>
> I enabled "resolve dependencies in workspace" for the project in the
> properties of the ivy.xml classpath container, but that seems to have no
> effect. I'm not sure where I'd look for a trace of the workspace
resolver's
> activities, but there's nothing in the log files, and the respective
> dependencies are resolved in the normal, download-the-artifact way.
>
>
> An obvious explanation would be if the workspace resolver doesn't work
on
> Maven projects -- nothing in the docs seems to confirm or deny that.
> Alternatively, I misconfigured something, in which case: how do I go
about
> debugging my configuration of IvyDE?
Does your maven project is managed by the M2Eclipse plugin or IvyDE ?
The workspace resolver will only work on projects that are managed by
IvyDE. More precisely, it will search for every Java project which has an
IvyDE dependency container configured. For instance it could work with an
M2Eclipse project which have also the Java nature, and in which there is a
IvyDE container; but this probably would make a classpath hell...
Nicolas