Eclipse Community Forums: AspectJ » Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2

Help

Home

Home » Language IDEs » AspectJ » Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2_07

Show: Today's Messages :: Show Polls :: Message Navigator

Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2_07 [message #55672]

Thu, 28 July 2005 10:02

Eclipse User

Originally posted by: Rainer.Burkart.ticos.ch

Hi Everybody,
I am working on large project (~9000 JAVA-classes) with Eclipse 3.1
(Release), AJDT 1.3 (Build 27.07.2005) and VM 1.4.2_07 (PC with 1 GByte of
physical memory)

Eclipse is handling this project pretty well so far.
Today I installed AJDT and tried to enable AspectJ for this project. I don't
have written any AspectJ-code so far, I just wanted to rebuild the project
right now. With AspectJ (AJDT) enabled, I had to increase memory settings
to -Vmx1024m, that Eclipse will not crash with OutOfMemory after some
minutes. (Without AJDT 768 MB is enough by far, compile time for the whole
project ~5 min at max).

Starting Build with AJDT enabled, I stopped the build (the hard way) after 3
hours. Memory consumption of the javaw.exe was moving up and down between
10MB and 950 MB several times during the build. Eclipse told me, that the
build was completed up to 50%, but after killing Eclipse, I could not find
even one .class file in my output directory.

I made a try with Eclipse 3.0.2 and AJDT 1.2 some time ago and I got the
same result. Eclipse could not finish the build at all.

Is there a way to get this to run ?

With kind regards, Rainer

Report message to a moderator

Re: Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2_07 [message #55699 is a reply to message #55672]

Thu, 28 July 2005 14:40

Eclipse User

Originally posted by: clemas.uk.ibm.com

Hi,

Are all 9000 in just one java project? that is a large project !

We have open bugs about memory consumption and a couple of strategies
for fixing it that we haven't gotten round to yet (its hard). The best
way to save memory would be to switch to an ANT build - remove the
aspectj builder and wire in the iajc task to build the project for you.
you will *not* get feedback on the UI about what was woven where - to
get around that you can perhaps turn on -showWeaveInfo to see the
weaving messages.

or you could not change your java project to an aspectj project and
instead create an aspectj project that contains solely your aspects -
you then add the output folder of your java project to the inpath for
the aspectj project. Then, when you build the aspectj project it will
apply the aspects to the last build of your java project.

Andy.
---
Andy Clement
AspectJ Dev

Rainer Burkart wrote:
> Hi Everybody,
> I am working on large project (~9000 JAVA-classes) with Eclipse 3.1
> (Release), AJDT 1.3 (Build 27.07.2005) and VM 1.4.2_07 (PC with 1 GByte of
> physical memory)
>
> Eclipse is handling this project pretty well so far.
> Today I installed AJDT and tried to enable AspectJ for this project. I don't
> have written any AspectJ-code so far, I just wanted to rebuild the project
> right now. With AspectJ (AJDT) enabled, I had to increase memory settings
> to -Vmx1024m, that Eclipse will not crash with OutOfMemory after some
> minutes. (Without AJDT 768 MB is enough by far, compile time for the whole
> project ~5 min at max).
>
> Starting Build with AJDT enabled, I stopped the build (the hard way) after 3
> hours. Memory consumption of the javaw.exe was moving up and down between
> 10MB and 950 MB several times during the build. Eclipse told me, that the
> build was completed up to 50%, but after killing Eclipse, I could not find
> even one .class file in my output directory.
>
> I made a try with Eclipse 3.0.2 and AJDT 1.2 some time ago and I got the
> same result. Eclipse could not finish the build at all.
>
> Is there a way to get this to run ?
>
> With kind regards, Rainer
>
>

Report message to a moderator

Re: Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2_07 [message #55727 is a reply to message #55699]

Fri, 29 July 2005 09:06

Eclipse User

Originally posted by: Rainer.Burkart.ticos.ch

Hi Andy,

the second hint helped a lot. Eclipse is doing it's job now. (It still
requires much more memory than the normal build without AspectJ)
Thank you very much for that fast support.

With kind regards, Rainer
BTW: Yes, all in one project. No problem for the Eclipse IDE. There are
others, which are not able to handle it....

"Andy Clement" <clemas@uk.ibm.com> schrieb im Newsbeitrag
news:dcaqo5$3kj$1@news.eclipse.org...
> Hi,
>
> Are all 9000 in just one java project? that is a large project !
>
> We have open bugs about memory consumption and a couple of strategies for
> fixing it that we haven't gotten round to yet (its hard). The best way to
> save memory would be to switch to an ANT build - remove the aspectj
> builder and wire in the iajc task to build the project for you. you will
> *not* get feedback on the UI about what was woven where - to get around
> that you can perhaps turn on -showWeaveInfo to see the weaving messages.
>
> or you could not change your java project to an aspectj project and
> instead create an aspectj project that contains solely your aspects - you
> then add the output folder of your java project to the inpath for the
> aspectj project. Then, when you build the aspectj project it will apply
> the aspects to the last build of your java project.
>
> Andy.
> ---
> Andy Clement
> AspectJ Dev
>
> Rainer Burkart wrote:
>> Hi Everybody,
>> I am working on large project (~9000 JAVA-classes) with Eclipse 3.1
>> (Release), AJDT 1.3 (Build 27.07.2005) and VM 1.4.2_07 (PC with 1 GByte
>> of physical memory)
>>
>> Eclipse is handling this project pretty well so far.
>> Today I installed AJDT and tried to enable AspectJ for this project. I
>> don't have written any AspectJ-code so far, I just wanted to rebuild the
>> project right now. With AspectJ (AJDT) enabled, I had to increase memory
>> settings to -Vmx1024m, that Eclipse will not crash with OutOfMemory after
>> some minutes. (Without AJDT 768 MB is enough by far, compile time for the
>> whole project ~5 min at max).
>>
>> Starting Build with AJDT enabled, I stopped the build (the hard way)
>> after 3 hours. Memory consumption of the javaw.exe was moving up and down
>> between 10MB and 950 MB several times during the build. Eclipse told me,
>> that the build was completed up to 50%, but after killing Eclipse, I
>> could not find even one .class file in my output directory.
>>
>> I made a try with Eclipse 3.0.2 and AJDT 1.2 some time ago and I got the
>> same result. Eclipse could not finish the build at all.
>>
>> Is there a way to get this to run ?
>>
>> With kind regards, Rainer

Report message to a moderator

Re: Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2_07 [message #55862 is a reply to message #55727]

Fri, 05 August 2005 23:15

Eclipse User

Originally posted by: david.goudreau.evant.com

How do you run unit tests, for example, in your 9000+ project with this
setup? I'm in a similar situation. The woven class files end up in the
output directory of your aspect project - how do you get them to run from
your non-aspect project if you want to run one of your unit tests?

-dmg

"Rainer Burkart" <Rainer.Burkart@ticos.ch> wrote in message
news:dccrip$7os$1@news.eclipse.org...
> Hi Andy,
>
> the second hint helped a lot. Eclipse is doing it's job now. (It still
> requires much more memory than the normal build without AspectJ)
> Thank you very much for that fast support.
>
> With kind regards, Rainer
> BTW: Yes, all in one project. No problem for the Eclipse IDE. There are
> others, which are not able to handle it....
>
> "Andy Clement" <clemas@uk.ibm.com> schrieb im Newsbeitrag
> news:dcaqo5$3kj$1@news.eclipse.org...
>> Hi,
>>
>> Are all 9000 in just one java project? that is a large project !
>>
>> We have open bugs about memory consumption and a couple of strategies for
>> fixing it that we haven't gotten round to yet (its hard). The best way
>> to save memory would be to switch to an ANT build - remove the aspectj
>> builder and wire in the iajc task to build the project for you. you will
>> *not* get feedback on the UI about what was woven where - to get around
>> that you can perhaps turn on -showWeaveInfo to see the weaving messages.
>>
>> or you could not change your java project to an aspectj project and
>> instead create an aspectj project that contains solely your aspects - you
>> then add the output folder of your java project to the inpath for the
>> aspectj project. Then, when you build the aspectj project it will apply
>> the aspects to the last build of your java project.
>>
>> Andy.
>> ---
>> Andy Clement
>> AspectJ Dev
>>
>> Rainer Burkart wrote:
>>> Hi Everybody,
>>> I am working on large project (~9000 JAVA-classes) with Eclipse 3.1
>>> (Release), AJDT 1.3 (Build 27.07.2005) and VM 1.4.2_07 (PC with 1 GByte
>>> of physical memory)
>>>
>>> Eclipse is handling this project pretty well so far.
>>> Today I installed AJDT and tried to enable AspectJ for this project. I
>>> don't have written any AspectJ-code so far, I just wanted to rebuild the
>>> project right now. With AspectJ (AJDT) enabled, I had to increase memory
>>> settings to -Vmx1024m, that Eclipse will not crash with OutOfMemory
>>> after some minutes. (Without AJDT 768 MB is enough by far, compile time
>>> for the whole project ~5 min at max).
>>>
>>> Starting Build with AJDT enabled, I stopped the build (the hard way)
>>> after 3 hours. Memory consumption of the javaw.exe was moving up and
>>> down between 10MB and 950 MB several times during the build. Eclipse
>>> told me, that the build was completed up to 50%, but after killing
>>> Eclipse, I could not find even one .class file in my output directory.
>>>
>>> I made a try with Eclipse 3.0.2 and AJDT 1.2 some time ago and I got the
>>> same result. Eclipse could not finish the build at all.
>>>
>>> Is there a way to get this to run ?
>>>
>>> With kind regards, Rainer
>
>

Report message to a moderator

Re: Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2_07 [message #55919 is a reply to message #55862]

Tue, 09 August 2005 11:57

Eclipse User

Originally posted by: Rainer.Burkart.ticos.ch

Hi,
Sorry for answering late, but I don't track the news every day....

I don't do any unit testing within this environment. I use AspectJ just for
finding the reasons for some strange behaviours of our software (like memory
leaks, perfomance issues, where debugging or profilers do not work because
of runtime constraints). For doing this, I have to integrate the complete
thing into a target system (distributed system).

So, I take the woven class files into the JAR instead the original ones,
that's it. No way (and no need currently) of testing this within the
IDE-environment.....

With kind regards, Rainer

"David Goudreau" <david.goudreau@evant.com> schrieb im Newsbeitrag
news:dd0ru3$c9f$1@news.eclipse.org...
> How do you run unit tests, for example, in your 9000+ project with this
> setup? I'm in a similar situation. The woven class files end up in the
> output directory of your aspect project - how do you get them to run from
> your non-aspect project if you want to run one of your unit tests?
>
>
> -dmg
>
>
> "Rainer Burkart" <Rainer.Burkart@ticos.ch> wrote in message
> news:dccrip$7os$1@news.eclipse.org...
>> Hi Andy,
>>
>> the second hint helped a lot. Eclipse is doing it's job now. (It still
>> requires much more memory than the normal build without AspectJ)
>> Thank you very much for that fast support.
>>
>> With kind regards, Rainer
>> BTW: Yes, all in one project. No problem for the Eclipse IDE. There are
>> others, which are not able to handle it....
>>
>> "Andy Clement" <clemas@uk.ibm.com> schrieb im Newsbeitrag
>> news:dcaqo5$3kj$1@news.eclipse.org...
>>> Hi,
>>>
>>> Are all 9000 in just one java project? that is a large project !
>>>
>>> We have open bugs about memory consumption and a couple of strategies
>>> for fixing it that we haven't gotten round to yet (its hard). The best
>>> way to save memory would be to switch to an ANT build - remove the
>>> aspectj builder and wire in the iajc task to build the project for you.
>>> you will *not* get feedback on the UI about what was woven where - to
>>> get around that you can perhaps turn on -showWeaveInfo to see the
>>> weaving messages.
>>>
>>> or you could not change your java project to an aspectj project and
>>> instead create an aspectj project that contains solely your aspects -
>>> you then add the output folder of your java project to the inpath for
>>> the aspectj project. Then, when you build the aspectj project it will
>>> apply the aspects to the last build of your java project.
>>>
>>> Andy.
>>> ---
>>> Andy Clement
>>> AspectJ Dev
>>>
>>> Rainer Burkart wrote:
>>>> Hi Everybody,
>>>> I am working on large project (~9000 JAVA-classes) with Eclipse 3.1
>>>> (Release), AJDT 1.3 (Build 27.07.2005) and VM 1.4.2_07 (PC with 1 GByte
>>>> of physical memory)
>>>>
>>>> Eclipse is handling this project pretty well so far.
>>>> Today I installed AJDT and tried to enable AspectJ for this project. I
>>>> don't have written any AspectJ-code so far, I just wanted to rebuild
>>>> the project right now. With AspectJ (AJDT) enabled, I had to increase
>>>> memory settings to -Vmx1024m, that Eclipse will not crash with
>>>> OutOfMemory after some minutes. (Without AJDT 768 MB is enough by far,
>>>> compile time for the whole project ~5 min at max).
>>>>
>>>> Starting Build with AJDT enabled, I stopped the build (the hard way)
>>>> after 3 hours. Memory consumption of the javaw.exe was moving up and
>>>> down between 10MB and 950 MB several times during the build. Eclipse
>>>> told me, that the build was completed up to 50%, but after killing
>>>> Eclipse, I could not find even one .class file in my output directory.
>>>>
>>>> I made a try with Eclipse 3.0.2 and AJDT 1.2 some time ago and I got
>>>> the same result. Eclipse could not finish the build at all.
>>>>
>>>> Is there a way to get this to run ?
>>>>
>>>> With kind regards, Rainer
>>
>>
>
>

Report message to a moderator

Re: Can't compile large Project with Eclipse3.1 + AJDT 1.3 + VM 1.4.2_07 [message #589718 is a reply to message #55672]

Thu, 28 July 2005 14:40

Andrew Clement

Messages: 162
Registered: July 2009

Senior Member

Hi,

Are all 9000 in just one java project? that is a large project !

We have open bugs about memory consumption and a couple of strategies
for fixing it that we haven't gotten round to yet (its hard). The best
way to save memory would be to switch to an ANT build - remove the
aspectj builder and wire in the iajc task to build the project for you.
you will *not* get feedback on the UI about what was woven where - to
get around that you can perhaps turn on -showWeaveInfo to see the
weaving messages.

or you could not change your java project to an aspectj project and
instead create an aspectj project that contains solely your aspects -
you then add the output folder of your java project to the inpath for
the aspectj project. Then, when you build the aspectj project it will
apply the aspects to the last build of your java project.

Andy.
---
Andy Clement
AspectJ Dev

Rainer Burkart wrote:
> Hi Everybody,
> I am working on large project (~9000 JAVA-classes) with Eclipse 3.1
> (Release), AJDT 1.3 (Build 27.07.2005) and VM 1.4.2_07 (PC with 1 GByte of
> physical memory)
>
> Eclipse is handling this project pretty well so far.
> Today I installed AJDT and tried to enable AspectJ for this project. I don't
> have written any AspectJ-code so far, I just wanted to rebuild the project
> right now. With AspectJ (AJDT) enabled, I had to increase memory settings
> to -Vmx1024m, that Eclipse will not crash with OutOfMemory after some
> minutes. (Without AJDT 768 MB is enough by far, compile time for the whole
> project ~5 min at max).
>
> Starting Build with AJDT enabled, I stopped the build (the hard way) after 3
> hours. Memory consumption of the javaw.exe was moving up and down between
> 10MB and 950 MB several times during the build. Eclipse told me, that the
> build was completed up to 50%, but after killing Eclipse, I could not find
> even one .class file in my output directory.
>
> I made a try with Eclipse 3.0.2 and AJDT 1.2 some time ago and I got the
> same result. Eclipse could not finish the build at all.
>
> Is there a way to get this to run ?
>
> With kind regards, Rainer
>
>

Report message to a moderator