Bug 265999

Summary:	Using I20090224-0800 build osgi has compile errors
Product:	[Eclipse Project] Equinox	Reporter:	Thomas Watson <tjwatson>
Component:	Framework	Assignee:	equinox.framework-inbox <equinox.framework-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Thomas Watson

2009-02-24 13:58:07 EST

JDT fixed some bugs WRT warning/errors in unused code.  As a result we have the following compile error when org.eclipse.osgi is checked out in a workspace:

The constructor AdminPermission.SignerProperty(String) is never used locally	AdminPermission.java	org.eclipse.osgi/osgi/src/org/osgi/framework	line 856	Java Problem

In this case the method is accessed by the OSGi Filter implementation using reflection to construct a matching value in a filter from a String.  Not sure how we should address this.  We may need to change the error to a warning for this project.

Comment 1 BJ Hargrave

2009-02-24 14:40:13 EST

Just put a @SuppressWarning annotation on it :-)

Comment 2 Thomas Watson

2009-02-24 17:41:46 EST

I changed this error to a warning in the osgi project.  I will open a separate bug against JTD to consider adding some javadoc tag that can be use to suppress this warning/error for a particular method/field.

Comment 3 Thomas Watson

2009-02-25 09:18:44 EST

I opened JDT bug 266132 to consider a javadoc tag or some other way to suppress the warning for a particular method.

Comment 4 Eclipse Webmaster

2019-09-06 16:09:32 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 5 Eclipse Genie

2021-09-03 03:16:10 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.