Bug 395093 - LTW classpath not properly computed when there are optional maven dependencies
Summary: LTW classpath not properly computed when there are optional maven dependencies
Status: NEW
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: 2.2.1   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: 2.2.4   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-26 12:25 EST by Andrew Eisenberg CLA
Modified: 2013-07-03 15:41 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Eisenberg CLA 2012-11-26 12:25:27 EST 
As described here:
http://www.eclipse.org/forums/index.php?t=rview&goto=987370#msg_987370

So, we have this situation in the workspace:

Project A (is the load time weaving app with the disabled maven profile)

Project A has a compile-time dependency to project B in the workspace.

Project B has an *optional* compile-time dependency to project C in the workspace.

Project C has a lot of other compile-time dependencies.

(Resolving dependencies from workspace projects is enabled in all projects.)

What I'm seeing is that the aspect classpath (-Daj.class.path) and the normal classpath (-classpath) on the commandline of project A contains the project C dependency and the transitive dependencies of C.

As far as I understand optional dependencies in Maven, this should not happen. Project C and its dependencies should not be included in the classpaths of A.

The dependeny hierachy view of the m2e POM editor does not seem to have this problem.
Comment 1 Andrew Eisenberg CLA 2013-02-22 13:56:45 EST 
Moving to 2.2.3.
Comment 2 Andrew Eisenberg CLA 2013-07-03 15:41:58 EDT 
Consider for the 2.2.4 release.