Which template has the error? The jdt prefs template at (http://www.eclipse.org/equinox/documents/org.eclipse.jdt.core.prefs) has the following values for discouraged and forbidden access:
org.eclipse.jdt.core.compiler.problem.discouragedReference=error
org.eclipse.jdt.core.compiler.problem.forbiddenReference=error
On another note I find it inconvenient that we set "Signal overriding or
implementing deprecated method" to warning. In some cases we have
interfaces which have deprecated methods, there is no choice for the
implementer, they must implement the deprecated method.
Tom
Jeff McAffer
<[EMAIL PROTECTED]
ibm.com> To
Sent by: [email protected]
equinox-dev-bounc cc
[EMAIL PROTECTED]
Subject
[equinox-dev] restricted access
08/28/2007 11:40 setttings
PM
Please respond to
Equinox
development
mailing list
<[EMAIL PROTECTED]
pse.org>
I was playing around in the provisioning test bundle and spent about 1 hour
tracking down a classloading issues that turned out to be a missing package
import. This should have shown up as an error but it turns out that the
Test project has forbidden access set to Warning instead of Error. Please
be sure that all projects conform to the Equinox coding guidelines (the
template has it as error). Where there are deviations, let people know.
for example, I left the test project set as Warning for discouraged use as
tests sometimes need to reach in to access things not normally available.
It might be worthwhile somehow scannng the projects to confirm that they
are all set appropriately. Perhaps a simple tool that just looks at the
relevant settings files?
Jeff _______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: pic23245.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
