| Eclipse 3.1 and auto-build [message #219011] |
Wed, 16 November 2005 10:19  |
Eclipse User |
|
|
|
Originally posted by: harry.sheng.sanmina-sci.om
Hi,
I have an AspectJ project, a java project and a web project in the Eclipse
3.1 workspace. The AspectJ project relies on the java project, the web
project relies on the AspectJ project and the java project.
The "build automatically" is enabled for the workspace. I noticed that
when I save changes to a .java file in the java project, the AspectJ
project is also automatically recompiled.
Because of the AspectJ compiler performance, it takes relatively long time
to save changes to .java file. Is it possible to prevent the AspectJ
project from auto-recompling when I save changes to .java file? I'd rather
do a clean build on AspectJ project later.
Thanks,
Harry
|
|
|
| Re: Eclipse 3.1 and auto-build [message #219034 is a reply to message #219011] |
Wed, 16 November 2005 13:21  |
| Eclipse User |
|
|
|
Originally posted by: john.eclipsefaq.org
There is infrastructure to support builders being told not to respond to
autobuild, but each builder must opt-in to allowing it. I.e., I suggest
entering an enhancement request against AspectJ to make their builders
"configurable". You can reference this bug report on the subject:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=82405
In the meantime, you can try this "hack": Edit the .project file for
your project. You should see a "buildCommand" tag for the AspectJ
builder. Add the following sub-element to this element:
<triggers>clean,full,incremental</triggers>
Here is an example of the Java builder configured this way:
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<triggers>clean,full,incremental</triggers>
<arguments>
</arguments>
</buildCommand>
NOTE: Some builders may not respond well to being turned off
unexpectedly. The best approach is to enter an enhancement request in
bugzilla against AspectJ for them to support this.
--
harry sheng wrote:
> Hi,
>
> I have an AspectJ project, a java project and a web project in the
> Eclipse 3.1 workspace. The AspectJ project relies on the java project,
> the web project relies on the AspectJ project and the java project.
>
> The "build automatically" is enabled for the workspace. I noticed that
> when I save changes to a .java file in the java project, the AspectJ
> project is also automatically recompiled.
> Because of the AspectJ compiler performance, it takes relatively long
> time to save changes to .java file. Is it possible to prevent the
> AspectJ project from auto-recompling when I save changes to .java file?
> I'd rather do a clean build on AspectJ project later.
>
> Thanks,
> Harry
>
>
|
|
|
| Re: Eclipse 3.1 and auto-build [message #219427 is a reply to message #219034] |
Fri, 18 November 2005 12:19 |
| Eclipse User |
|
|
|
Hi, John
In my environment, it is the AspectJ project that relies on the java
project, the java project does not rely on the AspectJ.
My issue is, auto-building of java code in the java project triggers the
re-building of the AspectJ project; not the auto-building of java code in
the AspectJ project triggering the re-building of the AspectJ project
itself.
I want the AspectJ project not to respond to auto-building in the java
project. I believe this is the default in Eclipse 3.0. I liked this, and
separated java code and aspect code into different projects.
I want to constrains the affect of code change inside the project
regarding the auto-building. I would like my Eclipse 3.1 environment works
the same way as 3.0 does.
Thanks,
Harry
John Arthorne wrote:
> There is infrastructure to support builders being told not to respond to
> autobuild, but each builder must opt-in to allowing it. I.e., I suggest
> entering an enhancement request against AspectJ to make their builders
> "configurable". You can reference this bug report on the subject:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=82405
> In the meantime, you can try this "hack": Edit the .project file for
> your project. You should see a "buildCommand" tag for the AspectJ
> builder. Add the following sub-element to this element:
> <triggers>clean,full,incremental</triggers>
> Here is an example of the Java builder configured this way:
> <buildCommand>
> <name>org.eclipse.jdt.core.javabuilder</name>
> <triggers>clean,full,incremental</triggers>
> <arguments>
> </arguments>
> </buildCommand>
> NOTE: Some builders may not respond well to being turned off
> unexpectedly. The best approach is to enter an enhancement request in
> bugzilla against AspectJ for them to support this.
> --
> harry sheng wrote:
>> Hi,
>>
>> I have an AspectJ project, a java project and a web project in the
>> Eclipse 3.1 workspace. The AspectJ project relies on the java project,
>> the web project relies on the AspectJ project and the java project.
>>
>> The "build automatically" is enabled for the workspace. I noticed that
>> when I save changes to a .java file in the java project, the AspectJ
>> project is also automatically recompiled.
>> Because of the AspectJ compiler performance, it takes relatively long
>> time to save changes to .java file. Is it possible to prevent the
>> AspectJ project from auto-recompling when I save changes to .java file?
>> I'd rather do a clean build on AspectJ project later.
>>
>> Thanks,
>> Harry
>>
>>
|
|
|
Powered by
FUDForum. Page generated in 0.05319 seconds
Home