| Summary: | ajcore file produced when doing a headless build of AJDT on the 3.7 stream | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Andrew Eisenberg <andrew.eisenberg> | ||||
| Component: | AJBrowser | Assignee: | aspectj inbox <aspectj-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | aclement | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Andrew Eisenberg
Created attachment 188487 [details]
ajcore file
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? 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. |