|Feedback on AJDT 1.1.11 [message #581888]
||Wed, 21 July 2004 22:18
| Guillaume Pothier
Registered: July 2009
These days I have been trying AJDT 1.1.11 to see if I can use it in my
I had a couple of problems:
- (with incremental build and automatic buildturned on) If I invoke the
build command with the toolbar button, I first get a foreground
progress dialog that keeps me informed of the completion of the build
process; no problem so far, but once it finishes to compile and weave, a
background build process is launched. If I open the Progress view, I see
that an AspectJ build is in progress, bu there is no information about
progress (ie. the progress bar stays at 0%). After a minute or two of
build process, the item disappears form the progress view for a short
instant, and then reappears. I don't know if it means that it started
over again or not, as there is no progress indication. This occurs
several times, I didn't have the patience to wait until it all stopped...
- (with automatic build on, incremental build off): the AspectJ build
process is invoked whenever I save a file (normal), but I observe the
same phenomenon as above.
- In the project properties dialog, the AspectJ entry appears twice
after a while (I mean, noz it appears twicem but yesterday it appeared
Overall, working with AspectJ is not practival at the moment for my
project, because it is far too slow. I have a 1ghz P3 with 384m RAM,
256m allocated to Eclipse. My project has +/- 1500 classes, and only one
aspect that crosscuts less than 10% of the classes. An AspectJ build of
my project takes 1-2mn, with auto build and incremental build off.
Is the work in progress with the incremental compiler supposed to
improve this? Is there any chance that the memory consumption gets lower?
Powered by FUDForum
. Page generated in 0.01409 seconds