Hi Ulrich,
Thanks for the reply.
At 01:48 PM 21/11/2004 +0100, Ulrich Köster wrote:
>Moin Chuck,
>
>is your plugin touching files during the build? (Create, modify or
>delete). If the answer is Ja. You've created the loop.
>
Yes, it creates or modifies up to one file per Java source file.
I'm not sure that your explanation is correct. The loop only occurs when I
detect a processing error in my plugin and throw a CoreException to signal
that the build should terminate. If there is no error, and the new .java
files are create properly, then the build runs and terminates normally with
no looping. It is something related to what happens when the CoreException
is thrown that triggers the eternal rebuild.
Does that suggest anything else?
Cheers,
Chuck
>Let me explain what happens behind the scenes. (It doesn't matter where
>the loop starts.)
>
>1. Someone touches a file.
>2. Eclipse invokes a build to process the changes.
>3. The build creates files that are not derivated.
>4. Goto 1
>
>To avoid the loop make sure that the files you create are derivated.
>Not possible when you use an external tool.
>
>What happens during a build of a WOLips project with the ant builder.
>
>1. Save Application.java
>2. JavaBuilder: Compile Application.java to the bin folder
>3. WOLips Ant Builder: Copy Application.class into the jar (External
>resource changes for Eclipse == new build)
>4. JavaBuilder: Nothing to do
>5. WOLips Ant Builder: The changes are in a woa, framework, build or
>dist folder. Ignore them.
>
>
>Ulrich
>
>
>
>Am 20.11.2004 um 03:12 schrieb Chuck Hill:
>
>> Hi,
>>
>> I was _so_ hoping that RC would fix this but, for me, it did not. I've
>> also built 1.1.0.92 from CVS and the results are the same. This only
>> happens with a plug that I wrote that wraps an external process. I'm
>> quite
>> willing to believe that it is a bug in my poorly written plugin, but
>> I'm
>> not sure where to look.
>>
>> To test this I have:
>> 1. Created a new Eclipse installation (tried both 3.01 and the 3.1
>> stable
>> build)
>> 2. Created a new plain old Java project, added one class with one
>> method
>> that has an error that my plugin will catch
>> 3. Activated my plugin for this project and started a build.
>>
>> The build starts, my plugin shows the error in the Console and the
>> build
>> stops as it should. I then
>>
>> 2. Created a new WOLips project (WOApplication), added to Application
>> one
>> method that has an error that my plugin will catch
>> 4. Started a build (note that my plugin is not active for this project
>> at
>> this point).
>>
>> The build starts and finihses shortly.
>>
>>
>> 5. Activated my plugin for this project and started a build.
>>
>> The build starts, my plugin shows the error in the Console and the
>> build
>> starts, my plugin shows the error in the Console and the build starts,
>> my
>> plugin shows the error in the Console and the build starts, my plugin
>> shows
>> the error in the Console and the build starts... :-)
>>
>> I'm throwing a CoreException to signal that the build should stop and
>> I've
>> tried somee other exception and both the monitor and BuildManager to
>> stop!
>> but to no avail. The only thing that works is System.exit(1). Grin.
>>
>> Any suggestions on what I may be doing that is not playing nicely with
>> WOLips or, if the problem lies in WOLips, where I might look for it?
>> I've
>> scanned the builders and nothing jumped out at me.
>>
>>
>> Cheers,
>> Chuck
>>
>>
>>
>>
>>
>>
>>
>
>
--Chuck Hill chil..lobal-village.net Global Village Consulting Inc. http://www.global-village.net
This archive was generated by hypermail 2.0.0 : Sun Nov 21 2004 - 13:58:30 EST