[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] restricted access setttings
- From: Thomas Watson <tjwatson@xxxxxxxxxx>
- Date: Wed, 29 Aug 2007 08:30:15 -0500
- Delivered-to: email@example.com
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:
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.
Jeff McAffer ---08/28/2007 11:42:40 PM---I was playing around in the provisioning test bundle and spent about 1 hour tracking down a classloading issues that turned out
Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
08/28/2007 11:40 PM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
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?
equinox-dev mailing list