Hi
I have an Eclipse project A which has an eclipse project B on its build path.
Both Eclipse projects have their own Maven Dependencies.
I am finding that when I use Eclipse (File > Export) to generate an
ant build.xml for project A, the resulting build file defines a
<path id="Maven Dependencies.libraryclasspath"> which contains the
Maven Dependencies for project B, not project A.
This behaviour occurs with both the current plug in, and the old 0.01x series.
If I remove Project B from Project A's build path, the generated
build.xml does contain Project A's Maven Dependencies (as you'd
expect).
So the manual workaround is to do that, and cut/paste the resulting
dependencies.
Has anyone else encountered this?
cheers
Jason
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
