Eclipse export ant build file - missing dependencies
----------------------------------------------------
Key: MECLIPSE-446
URL: http://jira.codehaus.org/browse/MECLIPSE-446
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Environment: Eclipse Version: 3.3.1.1, Build id: M20071023-1652
m2eclipse 0.92
Reporter: jason harrop
Priority: Minor
Attachments: testcase.tar.gz
I have an Eclipse project TestProjectA which has an eclipse project
TestProjectB 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 happens if the Java Build Path dialog, Order and Export tab, for Project A
has TestProjectB listed higher up than Maven Dependencies.
It does not matter whether TestProjectB exports its Maven Depencies or not.
In other words, the build.xml generated for TestProjectA only ever contains one
Maven Dependencies.libraryclasspath, and this will incorrectly list the maven
depencies for just TestProjectB if TestProjectB is listed higher than
MavenDependencies in TestProjectA's Order & Export tab.
If TestProjectB is listed lower than MavenDependencies in TestProjectA's Order
& Export tab, then TestProjectB's maven dependencies will not appear at all,
although they should if it is set to export them.
This behaviour occurs with both the current plug in, and the old 0.01x series.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
