Jason Harrop wrote:
I have an Eclipse project A which has an eclipse project B on its build path.
Both Eclipse projects have their own Maven Dependencies.
First of all, you shouldn't have project B in the build path of
project A, but artifact corresponding to project B should be listed in
the pom.xml for project A or else there isn't much value to use Maven
dependency management for those projects.
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?
It is not exactly clear to me how your projects actually look like,
but I could be an issue with Ant script generation provided by Eclipse
Platform. If you want us to investigate this, please open jira issue and
attach test Eclipse projects that would allow us to reproduce this.
regards,
Eugene
PS: by the way, why would you want to export Maven project as an Ant script?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
