Bug 23357

Summary:	Build not triggered on build path change
Product:	[Eclipse Project] JDT	Reporter:	Dirk Baeumer <dirk_baeumer>
Component:	Core	Assignee:	Jerome Lanneluc <jerome_lanneluc>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.0
Target Milestone:	2.1 M1
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Dirk Baeumer

2002-09-10 07:55:34 EDT

Use latest 2.1 build that has UI for circular project dependencies.

- create JUnit
- create JUnit2
- create a circular project dependency
- Check "Abort building...."
- Auto Compile kicks in
  observe: you get errors
- Change severity of build path problems from Error to Warning
- Auto Compile kicks in
  obvserve: the markers change
- Uncheck "Abort building..."
- Auto Compile kicks in
  observe: errors/warnings do not go away.

Comment 1 Jerome Lanneluc

2002-09-10 09:44:10 EDT

A full build is required to remove the 'Project was not build due to classpath 
errors' errors. Dirk, did you answer Yes when asked if you wanted to do a full 
build?

Comment 2 Jerome Lanneluc

2002-09-10 10:23:26 EDT

Actually the second full build (i.e. after changing severity of build path 
problems from Error to Warning) should have removed the error markers.

Comment 3 Dirk Baeumer

2002-09-10 10:31:02 EDT

Yup I answered Yes.

Comment 4 Jerome Lanneluc

2002-09-10 10:48:07 EDT

We were looking at the build state of prereq projects. In this case, the prereq 
project's build state was null and thus we refused to build the project.

Changed behavior to allow build even if the project's build state is null in 
the case of a 'warning' cycle (and the prereq project is involved in this 
cycle).

Comment 5 Jerome Lanneluc

2002-09-10 11:13:40 EDT

Fix backported to 2.0.x maintenance stream.

Comment 6 Philipe Mulet

2002-09-13 11:49:22 EDT

This is only a secondary part of the original bug 23318 (bug in the fix).

Comment 7 David Audel

2002-09-19 05:57:05 EDT

Verified.