| hidden-field preference? [message #19123] |
Sat, 10 May 2003 19:06  |
Eclipse User |
|
|
|
I just stepped up to I20030507 from 2.1 final, and got a ton of
warnings! In my workspace I have 1 public static final String
copyright per class, and a lot of classes, which means >700 warnings
like
> The field Foo.copyright is hiding a field from type Bar
I thought I could hide these with some setting in Prefs>Java>Compiler,
but even after I set everything to Ignore, I still get these warnings.
Is there another way to ignore or filter these warnings (without
filtering all warnings)? Or should I make a bug report/feature request?
|
|
|
|
| Re: hidden-field preference? [message #19644 is a reply to message #19137] |
Mon, 12 May 2003 04:52  |
| Eclipse User |
|
|
|
This diagnosis was recently introduced, and left as a warning by default for
testing purpose, until some UI preference is added (should occur soon).
Once UI is available, we will have it default to 'ignore'. Remember that
these integration builds are meant for testing.
"Jonathan Gossage" <jgossage@magma.ca> wrote in message
news:b9l5lf$3vd$1@rogue.oti.com...
>
> "Tom Roche" <tlroche@us.ibm.com> wrote in message
> news:b9k0lo$h91$1@rogue.oti.com...
> > I just stepped up to I20030507 from 2.1 final, and got a ton of
> > warnings! In my workspace I have 1 public static final String
> > copyright per class, and a lot of classes, which means >700 warnings
> > like
> >
> > > The field Foo.copyright is hiding a field from type Bar
> >
> > I thought I could hide these with some setting in Prefs>Java>Compiler,
> > but even after I set everything to Ignore, I still get these warnings.
> > Is there another way to ignore or filter these warnings (without
> > filtering all warnings)? Or should I make a bug report/feature request?
> >
> You can use the task filter to get rid of the entries in the task list,
but
> this will do nothing for the problem markers. If the strings are just
there
> for legal purposes and do not have to be accessed programmatically, just
> make them private instead of public.
>
>
|
|
|
| Re: hidden-field preference? [message #19689 is a reply to message #19644] |
Mon, 12 May 2003 04:58 |
| Eclipse User |
|
|
|
Note: one thing you can do to disable these extra diagnosis is:
1. shutdown Eclipse
2. edit the saved preference file:
<workspace>\.metadata\.plugins\org.eclipse.jdt.core\pref_store.ini
and append the following 2 lines:
------------
org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore
org.eclipse.jdt.core.compiler.problem.localVariableHiding=ig nore
------------
3. restart Eclipse, and rebuild all
"Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
news:b9nnf1$br5$1@rogue.oti.com...
> This diagnosis was recently introduced, and left as a warning by default
for
> testing purpose, until some UI preference is added (should occur soon).
> Once UI is available, we will have it default to 'ignore'. Remember that
> these integration builds are meant for testing.
>
> "Jonathan Gossage" <jgossage@magma.ca> wrote in message
> news:b9l5lf$3vd$1@rogue.oti.com...
> >
> > "Tom Roche" <tlroche@us.ibm.com> wrote in message
> > news:b9k0lo$h91$1@rogue.oti.com...
> > > I just stepped up to I20030507 from 2.1 final, and got a ton of
> > > warnings! In my workspace I have 1 public static final String
> > > copyright per class, and a lot of classes, which means >700 warnings
> > > like
> > >
> > > > The field Foo.copyright is hiding a field from type Bar
> > >
> > > I thought I could hide these with some setting in Prefs>Java>Compiler,
> > > but even after I set everything to Ignore, I still get these warnings.
> > > Is there another way to ignore or filter these warnings (without
> > > filtering all warnings)? Or should I make a bug report/feature
request?
> > >
> > You can use the task filter to get rid of the entries in the task list,
> but
> > this will do nothing for the problem markers. If the strings are just
> there
> > for legal purposes and do not have to be accessed programmatically, just
> > make them private instead of public.
> >
> >
>
>
|
|
|
| new .metadata appends, was: hidden-field preference? [message #23551 is a reply to message #19689] |
Wed, 14 May 2003 15:23 |
| Eclipse User |
|
|
|
Tom Roche wrote:
>>> I thought I could hide these [warnings new in I20030507] with some
>>> setting in Prefs>Java>Compiler, but even after I set everything to
>>> Ignore, I still get these warnings. Is there another way to ignore
>>> or filter these warnings (without filtering all warnings)?
Jonathan Gossage wrote:
>> If the strings are just there for legal purposes and do not have to
>> be accessed programmatically, just make them private instead of
>> public.
Actually I tried that before posting: it doesn't cause the warnings to
go away. (Which does kinda seem buglike ...)
Philippe Mulet wrote:
> Note: one thing you can do to disable these extra diagnosis is:
> 1. shutdown Eclipse
> 2. edit the saved preference file:
> <workspace>\.metadata\.plugins\org.eclipse.jdt.core\pref_store.ini
> and append the following 2 lines:
> ------------
> org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore
> org.eclipse.jdt.core.compiler.problem.localVariableHiding=ig nore
> ------------
> 3. restart Eclipse, and rebuild all
Yay! Works as advertised. However, now I notice all the _other_ couple
thousand of new warnings :-)
So, I'm wondering: are there any other .metadata warning appends that
one might use? Feel free to point to documentation (but I'm guessing
that this is not yet documented).
Thanks for your assistance!
|
|
|
Powered by
FUDForum. Page generated in 0.03735 seconds
Home