| Summary: | Error for API addition gets wrongly reported | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Dani Megert <daniel_megert> | ||||
| Component: | API Tools | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | darin.eclipse, Olivier_Thomann | ||||
| Version: | 3.5 | ||||||
| Target Milestone: | 3.5 M3 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dani Megert
yes, 2) would be a consequence of 1). I am investigating. I also get this in the .log: !ENTRY org.eclipse.pde.api.tools 4 0 2008-10-22 12:03:06.483 !MESSAGE Unable to resolve method signature: org.eclipse.ltk.ui.refactoring.LanguageElementNode#void internalAddChild(ChildNode) I also reproduce this issue. I am investigating. We are wrongly retrieving the restrictions for the method on the baseline. I need to find out why we don't see the method as @noreference in the baseline. Sorry this is the opposite. @noreference is retrieved for the the baseline, but an exception occurred while reading the api description for the current workspace. Then the method in the workspace is not seen as @noreference and therefore it is reported as a api addition. This is why we end up with the @since tag check. I am investigating the failure in the api description decoding. The .api_description entry for this method looks like:
<type handle="=org.eclipse.ltk.ui.refactoring/src<org.eclipse.ltk.ui.refactoring{LanguageElementNode.java[LanguageElementNode" modificationStamp="2" restrictions="0" visibility="0">
<method name="internalAddChild" restrictions="2048" signature="(QChildNode;)V" visibility="0"/>
</type>
It might be related to the unresolved parameter types.
Created attachment 115823 [details]
Proposed fix
Released for 3.5M3. Darin, please verify. Verified in N20081023-2000. |