Summary: | [javadoc][assist] @linkplain no longer proposed when 1.4 compliance is used | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> | ||||||
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> | ||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||
Severity: | major | ||||||||
Priority: | P3 | CC: | eclipse | ||||||
Version: | 3.1 | ||||||||
Target Milestone: | 3.2 M5 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Dani Megert
2006-01-09 08:38:07 EST
Created attachment 32675 [details]
Patch to fix this issue
Specific eclipse patch format including 2 projects:
- org.eclipse.jdt.core
- org.eclipse.jdt.core.tests.model
Problem came from the fact that comment parsers used sourceLevel instead of compliance level. As default used for compliance 1.4 is source level 1.3, parser wrongly thought that it only has to propose 1.3 compliance level tags...
So waiting for fix which will in tomorrow's integration build, the workaround is to set sourceLevel explicitely to 1.4...
Created attachment 32757 [details]
New patch to fix this issue
Previous patch has some undesirable side effects...
This one is more precise and pass all JDT/Core and JDT/UI tests.
Released in HEAD Verified for 3.2 M5 using build I20060214-0010 |