RE: [Acegisecurity-developer] Proposal: Resolving Eclipse IDE warnings

2005-11-11 Thread scott
@lists.sourceforge.net Subject: Re: [Acegisecurity-developer] Proposal: Resolving Eclipse IDE warnings +1 post 0.9.0 We should do one Checkout, Jalopy and commit operation on the whole tree first off... On 11/6/05, Ben Alex [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: When using Eclipse 3.1

Re: [Acegisecurity-developer] Proposal: Resolving Eclipse IDE warnings

2005-11-06 Thread Vijay Varadan
+1 Agree - I would appreciate this greatly.On 11/6/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:When using Eclipse 3.1 there are quite a few (520) source code warnings displayed in the Problems view.At some point I'd like to resolve as many of these as makes sense (likeunuseed imports) and then

RE: [Acegisecurity-developer] Proposal: Resolving Eclipse IDE warnings

2005-11-06 Thread scott
46 PMTo: acegisecurity-developer@lists.sourceforge.netSubject: Re: [Acegisecurity-developer] Proposal: Resolving Eclipse IDE warnings +1 Agree - I would appreciate this greatly. On 11/6/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: When using Eclipse 3.1 there are quite a few (5

Re: [Acegisecurity-developer] Proposal: Resolving Eclipse IDE warnings

2005-11-06 Thread Ben Alex
[EMAIL PROTECTED] wrote: When using Eclipse 3.1 there are quite a few (520) source code warnings displayed in the Problems view. At some point I'd like to resolve as many of these as makes sense (like unuseed imports) and then to update the .settings/org.eclipse.jdt.core.prefs file to ignore