Bug 8812

Summary: Changing export state not propagated
Product: [Eclipse Project] JDT Reporter: Dani Megert <daniel_megert>
Component: CoreAssignee: Philipe Mulet <philippe_mulet>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: P1    
Version: 2.0   
Target Milestone: 2.0 M3   
Hardware: PC   
OS: Windows NT   
Whiteboard:

Description Dani Megert CLA 2002-01-31 04:19:28 EST 
1. Auto-build on
2. Create J project A with junit.jar on build path
3. Create J project B with new class C
4. Try to add a JUnit class to C with code assist ==> does not work (OK)
5. Change A to export junit.jar
4. Try to add a JUnit class to C with code assist ==> does not work
This is wrong, it should work.

I now have to force a build of project B to be able to continue work.
Comment 1 Dani Megert CLA 2002-01-31 04:26:23 EST 
Two additional remarks (which made me change the severity to critical)

1. It was not the build that fixed the problem. Actually not even a full build
fixes the problem! You have to open B's properties and save them again

2. The problem is with code assist. I can add classes via code assist and then
the compiler complains correctly. Even after showing me error ticks I can use
code assist to add classes out of scope unless I touch the project build path.
Comment 2 Philipe Mulet CLA 2002-01-31 05:34:36 EST 
Which build was this in ?
You need to put A on the classpath of project B.
Comment 3 Dani Megert CLA 2002-01-31 06:46:33 EST 
Sorry:
- Build I20020129
- and of course: add project A on the classpath of project B when creating B
Comment 4 Philipe Mulet CLA 2002-02-01 13:08:01 EST 
Bug was that if the only change was on the export flag, we did not force to 
refresh dependent projects.
Good find.
Fixed.