Annotations for language features
ted at tedneward.com
Sun Aug 16 22:55:51 PDT 2009
Dude, "getenv" was marked deprecated for a decade. :-)
Seriously, I'm *not* trying to point fingers or cast blame, I'm just trying
to point out that the messaging around a feature needs to be loud, clear,
and unambiguous to avoid this kind of argument/debate/discussion later.
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
> -----Original Message-----
> From: Joe.Darcy at Sun.COM [mailto:Joe.Darcy at Sun.COM]
> Sent: Sunday, August 16, 2009 10:36 PM
> To: Ted Neward
> Cc: 'Adam Malter'; coin-dev at openjdk.java.net
> Subject: Re: Annotations for language features
> Ted Neward wrote:
> >> The apt tool and API was always planned to be "the one we throw
> >> in
> >> the "The Mythical Man-Month" sense, which is why it has been
> >> in JDK 7 and is planned for removal in a future JDK release.
> > In hindsight, that's easy to say; I don't remember any sort of
> statement to
> > that effect when it was first shipped. I'm not making accusations or
> First, the apt API is a com.sun.* API and not an official java or javax
> API; second, since shipping in JDK 5 the apt javadoc has stated "Note
> that the apt tool and its associated APIs may be changed or superseded
> in future j2se releases:"
> > espousing conspiracy theories, I just simply want to raise the idea
> that apt
> > was viewed by many--including me--as "the" Sun-blessed way to write
> > annotation processors.
> It was in JDK 5 and ceased to be the recommended way to write
> processors once JSR 269 shipped in JDK 6.
More information about the coin-dev