Summary: | No classpath marker produced when cycle through PDE container | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> | ||||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | kent_johnson, t.p.ellison | ||||||
Version: | 3.2 | ||||||||
Target Milestone: | 3.2 M3 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Philipe Mulet
2005-10-19 04:55:15 EDT
Created attachment 28430 [details]
Builder + CPInit traces
Note: when creating plain Java projects, and manually setting circular dependencies, cycle markers are detected. Created attachment 28440 [details]
Patch against v_617
Tim, can you please try this patch and let me know if this fixes your problem ?
If you prefer a binary patch, let me know as well and I'll post a jdt.core
update.
Assuming I applied your patch correctly (loaded org.eclipse.jdt.core from CVS HEAD, and imported dependents from workspace, then applied patch and ran as Eclipse application)... This had no effect on the problem I see. The cycle warning markers are shown, however, on one launch I get a 'project cannot be built until prereq built' error, and then when launching again got an 'Access restriction' error. It wasn't supposed to address the entire problem, but at least reveal the cycle marker which were hidden in the past. Still there seem to be some remaining issue, as this should build in the end. Tim, can you please describe your problem in details in a separate bug ? The particular problem described by Philippe in comment 0 is now fixed. (Applyied attached patch and added regression test ClasspathTests#testCycleDetection4()) Cycling markers are now properly reported: A cycle was detected in the build path of project: AP1 AP1 A cycle was detected in the build path of project: AP2 AP2 A cycle was detected in the build path of project: AP3 AP3 Verified for 3.2 M3 using build I20051025-0800+JDT/Core v_618a |