I think so. If a recompile would make it work, then no need to update the @since. It would be lovely to say @improved 3.0; but at the end of the day I think we'll have to rely on separate documentation to handle that.
On Sun, Mar 7, 2010 at 12:22 AM, Gary Gregory <[email protected]> wrote: > Fair enough. > > What about APIs that change from, for example, String to CharSequence, should > these stay with the same @since tags, even if the Java version for the > project of the @since version did not include the class CharSequence. > > Gary > >> -----Original Message----- >> From: Henri Yandell [mailto:[email protected]] >> Sent: Saturday, March 06, 2010 19:23 >> To: Commons Developers List >> Subject: Re: [lang] v3.0 @since >> >> I think it does. >> >> The choice of a new package name was a workaround rather than a >> declaration of a different package, so the @since's still have value. >> >> Hen >> >> On Sat, Mar 6, 2010 at 5:13 PM, Gary Gregory >> <[email protected]> wrote: >> > Looking at trunk I see that the @since tags are still there. Since the >> package o.a.c.lang3 is new, does it make sense to have @since tags OTHER than >> 3.0 if any? >> > >> > Gary Gregory >> > Senior Software Engineer >> > Seagull Software >> > email: [email protected] >> > email: [email protected] >> > www.seagullsoftware.com >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
