Bug 336572 - ajcore file produced when doing a headless build of AJDT on the 3.7 stream
Summary: ajcore file produced when doing a headless build of AJDT on the 3.7 stream
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: AJBrowser (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-07 19:17 EST by Andrew Eisenberg CLA
Modified: 2011-02-08 12:05 EST (History)
1 user (show)

See Also:

Attachments
ajcore file (67.54 KB, text/plain)
2011-02-07 19:18 EST, Andrew Eisenberg CLA 		no flags Details
View All 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 2011-02-07 19:17:12 EST 
ajc created the following ajcore file when compiling the org.eclipse.contribution.xref.core plugin headless.
Comment 1 Andrew Eisenberg CLA 2011-02-07 19:18:03 EST 
Created attachment 188487 [details]
ajcore file
Comment 2 Andrew Clement CLA 2011-02-08 11:30:56 EST 
After chewing on it for a bit, I do recall something like this before, when AspectJ is called from Ant.  I can't quite find the bug report at the moment though.

Are you using fork when running the AspectJ compile step?
Comment 3 Andrew Eisenberg CLA 2011-02-08 12:05:57 EST 
I'm not really sure...it is being run as part of a pde build.  I just had a look and it seems like there was no fork being called.  As you mentioned, it is very likely that two builds were occurring at once: a pde build and a standard build using the AJBuilder.

THe situation I had was a bit odd and not something that I expect will happen very often.  I was doing a headless pde build of AJDT and using a workspace that (inadvertently) already had some ApsectJ projects in it.  It is likey that there was a call to iajc and a call to build the AJ projects in the workspace occurring at the same time.