Community
Participate
Working Groups
I'm attaching a sample project demonstrating this bug. Unzip and import the project, right click on the project and change the selected jre for the builders. Then dirty/save Foo.java, you'll see that the defined ant builders get run twice (make the console view visible) - once before the java builder and once after (jar only gets updated in the one after). If you remove the first builder, then the remaning builder correctly runs only once after the java builder. This is on eclipse 3.0 on linux fedora core 2
Created attachment 14234 [details] project demonstarting bug
What types of builds are your builders set to be trigger on? Likely duplicate of bug 70650 (fixed in 3.0.1) or bug 71438 (to be fixed in 3.1 M2). Workaround is described in bug 70650 comment #14.
Triggering on all build types. Sounds similar - I'll grab 3.0.1RC1 and see if it fixes me. If not, I'll try with one of the 3.1 nightly builds
Actually, I just tried both patches from bug 70650, and the problem still exhibits itself with the attached project.
Thanks for the info. Correct me if I am wrong, but I believe your test case would indicate triggering on autobuild? Autobuild triggering is covered bug 71438 which we can fix next integration build with the changes in Core that were released today.
Correct - using autobuild - not sure if bug 71438 is completely applicable as by builders run both before AND after the javabuilder. But if you say it is, I'll trust you :) Might be worth trying the attached project after the fix just to make sure though.
No that is great :-) Explaination: The first autobuild builder gets notified and we run all the builders (don't ask) The java builder runs. Changes things The first autobuild builder gets notified of the changes, we run all the builders I will mark this as a duplicate and use it as my first test case. Thanks. If the integration build comes out today, I will try to have the fix in by Wednesday 3.1 nights build. *** This bug has been marked as a duplicate of 71438 ***
