Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 71645 - Java Builder does not execute in the correct order during a build
Summary: Java Builder does not execute in the correct order during a build
Status: RESOLVED DUPLICATE of bug 70650
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 71647 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-08-09 09:38 EDT by Brian Simoneau CLA
Modified: 2004-08-09 14:00 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Simoneau CLA 2004-08-09 09:38:32 EDT 
I have a Java project that requires external builders in the form of Ant file 
targets to run during a project build.  On the Builders screen under project 
Properties, the Java Builder and external builders are listed in the order that 
I need them to run in.  When I do a Clean... followed by a build, the Java 
Builder is always executed after all the other external builders are run.  This 
causes the build to fail because the source code needs to be compiled before 
the last two external builders are run.  
The project is set to Build Automatically and the external builders are all set 
to run After a "Clean".  I am using Version: 3.0.0, Build id: 200406251208.
Comment 1 Olivier Thomann CLA 2004-08-09 09:41:59 EDT 
Move to Platform/runtime
Comment 2 DJ Houghton CLA 2004-08-09 09:48:06 EDT 
Potential dup of bug 70650?
Comment 3 DJ Houghton CLA 2004-08-09 12:37:47 EDT 
*** Bug 71647 has been marked as a duplicate of this bug. ***
Comment 4 Brian Simoneau CLA 2004-08-09 13:42:50 EDT 
Yes, I am having the same problem as described in bug 70650.
Comment 5 DJ Houghton CLA 2004-08-09 14:00:11 EDT 

*** This bug has been marked as a duplicate of 70650 ***