Bug 288020

Summary:

Export Eclipse product/plugin with AspectJ support requires AJDE

Product:

[Tools] AJDT

Reporter:

Andrew Eisenberg <andrew.eisenberg>

Component:

Assignee:

AJDT-inbox <AJDT-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

iloncar.ml

Version:

2.0.0

Target Milestone:

2.0.1

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
calculate ajde.classpath from required bundles	andrew.eisenberg: iplog+

Description Andrew Eisenberg

2009-08-28 19:33:17 EDT

Exporting requires AJDE to be in the target platform, even if it is not being used.  This is less than optimal.  We should figure out what to do.  

At the very least, provide a warning to the user if AJDE is not included.  The best solution would be to go out and find the bundle to build against, but not include it in the target.

Comment 1 Ivica Loncar

2009-08-29 13:31:51 EDT

Since ajde.classpath is compile time dependency, and AJDE must only be available to the PDE build environment I suggest that ajde.classpath be computed from static AJDE dependencies (there's no need to resolve AJDE before computing ajde.classpath).

Comment 2 Ivica Loncar

2009-08-29 13:34:50 EDT

Created attachment 145998 [details]
calculate ajde.classpath from required bundles

Instead of trying to find resolved AJDE dependencies why don't we just take them, find bundles and create ajde.classpath.

Comment 3 Andrew Eisenberg

2009-09-01 12:04:48 EDT

Thanks for the patch.  I've applied it, tested it, and it seems to work.  This will be available in the next dev build.