Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318467 - Error icon on plugin.xml although only warning marker set
Summary: Error icon on plugin.xml although only warning marker set
Status: CLOSED WORKSFORME
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-30 09:32 EDT by Marko Tomljenovic CLA
Modified: 2010-06-30 16:21 EDT (History)
1 user (show)

See Also:

Attachments
PDE compiler preference (64.52 KB, image/png)
2010-06-30 09:32 EDT, Marko Tomljenovic CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marko Tomljenovic CLA 2010-06-30 09:32:09 EDT 
Build Identifier:   Eclipse Plug-in Development Environment	3.5.2.R35x_v20100119-7Z7_FA2FDX-aXQYWqYDBz-z0qufo	org.eclipse.pde.feature.group

I have an extension point where one of the attributes of one extension references an internal (discouraged) class.
Although the PDE compiler preferences are set to create a warning marker for discouraged access and the warning marker is created an error icon is created on the plugin.xml.

Reproducible: Always

Steps to Reproduce:
1. Set the PDE compiler preference for "References for discouraged access" to "Warning".
2. Create an extension of "org.eclipse.search.searchPages"
3. In the "class" attribute set "org.eclipse.search.internal.ui.text.TextSearchPage"
4. Now an error icon will be shown on the corresponding plugin.xml
Comment 1 Marko Tomljenovic CLA 2010-06-30 09:32:45 EDT 
Created attachment 173095 [details]
PDE compiler preference
Comment 2 Ankur Sharma CLA 2010-06-30 16:21:00 EDT 
I tested on Eclipse 3.4.2 and Eclipse 3.6 and it worked fine on both. Please test with Eclipse 3.6 and reopen this bug if you still face the issue. Also we will need more information about your plug-in as it seems to work fine with the 'steps to reproduce' mentioned.