[platform-swt-dev] Standards for imports, warnings, etc. for Eclipse/SWT

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[platform-swt-dev] Standards for imports, warnings, etc. for Eclipse/SWT?

From: Scott Kovatch <skovatch@xxxxxxxxx>
Date: Wed, 23 Sep 2009 09:01:23 -0700
Accept-language: en-US
Acceptlanguage: en-US
Delivered-to: platform-swt-dev@eclipse.org
Thread-index: Aco8ZxhnJ42umi+BTRanXeYhoBPEhQ==
Thread-topic: Standards for imports, warnings, etc. for Eclipse/SWT?

Hi,

Are there any standards (either Eclipse-wide or team-wide) for ignored warnings and other settings in Eclipse projects? I noticed Silenio fixed one my commits to remove unused packages in imports, which apparently triggered a bug. I don't mind the cleanup, but if I can set up my workspace so I don't have to watch for things like that I'm happy to do it.

I get bitten by this with my Adobe team now and then, and it seems like something that the IDE should make possible, either via exported settings or by using a prototype/template workspace.

Thanks,

Scott K.

----------

Scott Kovatch

Flex Engineering

skovatch@xxxxxxxxx

I am Scott Kovatch, and I approve this message.

Follow-Ups:
- Re: [platform-swt-dev] Standards for imports, warnings, etc. for Eclipse/SWT?
  - From: Chris Aniszczyk

Prev by Date: Re: [platform-swt-dev] Cocoa SWT_AWT issues, and a new API proposal
Next by Date: Re: [platform-swt-dev] Standards for imports, warnings, etc. for Eclipse/SWT?
Previous by thread: [platform-swt-dev] Cocoa SWT_AWT issues, and a new API proposal
Next by thread: Re: [platform-swt-dev] Standards for imports, warnings, etc. for Eclipse/SWT?
Index(es):
- Date
- Thread