>-Original Message-
>From: Oleg Khaschansky [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 11, 2006 2:32 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: RE: [classlib][suncompat] created
>
>Another solution is to create stubs which will throw exceptions with
&g
l Message-
>From: Alex Blewitt [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 11, 2006 12:06 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: RE: [classlib][suncompat] created
>
>I think the @deprecated is a good idea, but I strongly believe that we
>should *not* have
nov
Intel Middleware Product Division
>-Original Message-
>From: Alex Blewitt [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 11, 2006 12:06 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: RE: [classlib][suncompat] created
>
>I think the @deprecated is a good ide
I think the @deprecated is a good idea, but I strongly believe that we
should *not* have this as a default. There's an easy workaround for
the subset of applications that need it (e.g. enable it in the
.properties file) whilst still preventing new code from being able to
reference it. A simple FAQ
Sounds like a FAQ in the making :-)
On 10/08/06, Tim Ellison <[EMAIL PROTECTED]> wrote:
Alex Blewitt wrote:
> OK. What's the plan with regards to adding items in here e.g. Base64
> or tools like JavaC? Or do we just add them organically as we find
> problems?
Let's try and keep this JAR as smal
