Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AJDT » Feedback on AJDT 1.1.11
Feedback on AJDT 1.1.11 [message #38940] Wed, 21 July 2004 18:18 Go to next message
Guillaume Pothier is currently offline Guillaume Pothier
Messages: 107
Registered: July 2009
Senior Member
Hi,
These days I have been trying AJDT 1.1.11 to see if I can use it in my
project.
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
only once).

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?
Guillaume
Re: Feedback on AJDT 1.1.11 [message #38987 is a reply to message #38940] Thu, 22 July 2004 06:38 Go to previous messageGo to next message
Eclipse User
Originally posted by: clemas.uk.ibm.com

Guillaume Pothier wrote:
> Hi,
> These days I have been trying AJDT 1.1.11 to see if I can use it in my
> project.
> 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
> only once).
>
> 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?
> Guillaume

Hi,

I have seen the main issue you describe a few times - but I can not
reliably recreate it to debug it. For me these unwanted background
builds seem to occur now and again, rather than every time I do
something. If you are amenable to it, if you privately share your
project with us we will investigate as you seem to have a situation that
always causes it to occur.

Is the aspect a core part of your programs functionality or something
orthogonal like logging? It is very easy to set up the aspects in a
second project that weave into a base java project that contains all
your java code. If that would work for you I can go into more details.

The AspectJ compiler is fully incremental enabled. The AJDT tools are
not - they can't render incremental results correctly in the outline
view and that's why we don't currently have incremental set as the
default compilation option. If you are happy to have a incomplete
outline view then you can turn incremental on and the compiler will
always create the right results on disk for you to execute.

On the memory issue - I know we still have problems, and I think I know
where some of them are so there is still more work to do in this area.

let me know on email if you are OK to share your project.

cheers,
Andy.
Re: Feedback on AJDT 1.1.11 [message #39046 is a reply to message #38987] Thu, 22 July 2004 18:24 Go to previous messageGo to next message
Guillaume Pothier is currently offline Guillaume Pothier
Messages: 107
Registered: July 2009
Senior Member
Andy Clement wrote:
> I have seen the main issue you describe a few times - but I can not
> reliably recreate it to debug it. For me these unwanted background
> builds seem to occur now and again, rather than every time I do
> something. If you are amenable to it, if you privately share your
> project with us we will investigate as you seem to have a situation that
> always causes it to occur.
>

I am afraid I cannot share my project for the time being. But I must say
that I think my project is all the more classic: three source folders, a
few jars, I'm using the eclipse build process (I mean I don't use ant on
a regular basis), the project is shared via CVS... I cannot think of any
fancy setup...

> Is the aspect a core part of your programs functionality or something
> orthogonal like logging? It is very easy to set up the aspects in a
> second project that weave into a base java project that contains all
> your java code. If that would work for you I can go into more details.

I would be glad if you explained that trick to separate aspects and
source code.
For now I have only one aspect that does the following: there are some
objects on which I want to perform post-constructor initialization, ie.
call an init() method after they are fully instantiated (just after the
call to "new"). So I defined an interface IPCIObject with the init()
method, and I make a few classes implement that interface. I guess that
would be called core functionality.

>
> The AspectJ compiler is fully incremental enabled. The AJDT tools are
> not - they can't render incremental results correctly in the outline
> view and that's why we don't currently have incremental set as the
> default compilation option. If you are happy to have a incomplete
> outline view then you can turn incremental on and the compiler will
> always create the right results on disk for you to execute.


Well, whith incremental build and automatic build turned on, I just
added a whitespace in a file and saved it, and the build process seemed
to last forever... At least, I didn't wait for it to complete. Is the
backend incremental compiler a work in progress, or is it finished?

>
> On the memory issue - I know we still have problems, and I think I know
> where some of them are so there is still more work to do in this area.
>
Re: Feedback on AJDT 1.1.11 [message #39280 is a reply to message #39046] Sat, 24 July 2004 14:15 Go to previous message
Eclipse User
Originally posted by: clemas.uk.ibm.com

Guillaume Pothier wrote:
> Andy Clement wrote:
>>
>> The AspectJ compiler is fully incremental enabled. The AJDT tools are
>> not - they can't render incremental results correctly in the outline
>> view and that's why we don't currently have incremental set as the
>> default compilation option. If you are happy to have a incomplete
>> outline view then you can turn incremental on and the compiler will
>> always create the right results on disk for you to execute.
>
>
>
> Well, whith incremental build and automatic build turned on, I just
> added a whitespace in a file and saved it, and the build process seemed
> to last forever... At least, I didn't wait for it to complete. Is the
> backend incremental compiler a work in progress, or is it finished?
>

I wanted to add an extra comment on this. The incremental support in
the AspectJ compiler is fully functional. There may be some further
optimizations we can make when you save an aspect such that it does less
compilation but for day-to-day development when you are just modifying
classes or interfaces, it should work perfectly.

It is the way that incremental support surfaces in AJDT that seems to be
misbehaving. We have a bug report in on it already (70774) that I will
use for further investigations.

cheers,
Andy.
---
AspectJ/AJDT Committer
Re: Feedback on AJDT 1.1.11 [message #581948 is a reply to message #38940] Thu, 22 July 2004 06:38 Go to previous message
Andrew Clement is currently offline Andrew Clement
Messages: 162
Registered: July 2009
Senior Member
Guillaume Pothier wrote:
> Hi,
> These days I have been trying AJDT 1.1.11 to see if I can use it in my
> project.
> 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
> only once).
>
> 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?
> Guillaume

Hi,

I have seen the main issue you describe a few times - but I can not
reliably recreate it to debug it. For me these unwanted background
builds seem to occur now and again, rather than every time I do
something. If you are amenable to it, if you privately share your
project with us we will investigate as you seem to have a situation that
always causes it to occur.

Is the aspect a core part of your programs functionality or something
orthogonal like logging? It is very easy to set up the aspects in a
second project that weave into a base java project that contains all
your java code. If that would work for you I can go into more details.

The AspectJ compiler is fully incremental enabled. The AJDT tools are
not - they can't render incremental results correctly in the outline
view and that's why we don't currently have incremental set as the
default compilation option. If you are happy to have a incomplete
outline view then you can turn incremental on and the compiler will
always create the right results on disk for you to execute.

On the memory issue - I know we still have problems, and I think I know
where some of them are so there is still more work to do in this area.

let me know on email if you are OK to share your project.

cheers,
Andy.
Re: Feedback on AJDT 1.1.11 [message #581999 is a reply to message #38987] Thu, 22 July 2004 18:24 Go to previous message
Guillaume Pothier is currently offline Guillaume Pothier
Messages: 107
Registered: July 2009
Senior Member
Andy Clement wrote:
> I have seen the main issue you describe a few times - but I can not
> reliably recreate it to debug it. For me these unwanted background
> builds seem to occur now and again, rather than every time I do
> something. If you are amenable to it, if you privately share your
> project with us we will investigate as you seem to have a situation that
> always causes it to occur.
>

I am afraid I cannot share my project for the time being. But I must say
that I think my project is all the more classic: three source folders, a
few jars, I'm using the eclipse build process (I mean I don't use ant on
a regular basis), the project is shared via CVS... I cannot think of any
fancy setup...

> Is the aspect a core part of your programs functionality or something
> orthogonal like logging? It is very easy to set up the aspects in a
> second project that weave into a base java project that contains all
> your java code. If that would work for you I can go into more details.

I would be glad if you explained that trick to separate aspects and
source code.
For now I have only one aspect that does the following: there are some
objects on which I want to perform post-constructor initialization, ie.
call an init() method after they are fully instantiated (just after the
call to "new"). So I defined an interface IPCIObject with the init()
method, and I make a few classes implement that interface. I guess that
would be called core functionality.

>
> The AspectJ compiler is fully incremental enabled. The AJDT tools are
> not - they can't render incremental results correctly in the outline
> view and that's why we don't currently have incremental set as the
> default compilation option. If you are happy to have a incomplete
> outline view then you can turn incremental on and the compiler will
> always create the right results on disk for you to execute.


Well, whith incremental build and automatic build turned on, I just
added a whitespace in a file and saved it, and the build process seemed
to last forever... At least, I didn't wait for it to complete. Is the
backend incremental compiler a work in progress, or is it finished?

>
> On the memory issue - I know we still have problems, and I think I know
> where some of them are so there is still more work to do in this area.
>
Re: Feedback on AJDT 1.1.11 [message #582185 is a reply to message #39046] Sat, 24 July 2004 14:15 Go to previous message
Andrew Clement is currently offline Andrew Clement
Messages: 162
Registered: July 2009
Senior Member
Guillaume Pothier wrote:
> Andy Clement wrote:
>>
>> The AspectJ compiler is fully incremental enabled. The AJDT tools are
>> not - they can't render incremental results correctly in the outline
>> view and that's why we don't currently have incremental set as the
>> default compilation option. If you are happy to have a incomplete
>> outline view then you can turn incremental on and the compiler will
>> always create the right results on disk for you to execute.
>
>
>
> Well, whith incremental build and automatic build turned on, I just
> added a whitespace in a file and saved it, and the build process seemed
> to last forever... At least, I didn't wait for it to complete. Is the
> backend incremental compiler a work in progress, or is it finished?
>

I wanted to add an extra comment on this. The incremental support in
the AspectJ compiler is fully functional. There may be some further
optimizations we can make when you save an aspect such that it does less
compilation but for day-to-day development when you are just modifying
classes or interfaces, it should work perfectly.

It is the way that incremental support surfaces in AJDT that seems to be
misbehaving. We have a bug report in on it already (70774) that I will
use for further investigations.

cheers,
Andy.
---
AspectJ/AJDT Committer
Previous Topic:How to add aspects to multiple eclipse plugin projects?
Next Topic:Missing source file references in error messages
Goto Forum:
  


Current Time: Tue Jul 29 16:58:29 EDT 2014

Powered by FUDForum. Page generated in 0.14864 seconds