You could track in which version things had been added :-) I think we had to do that in Groovy. We weren't using @since very consistently, and we did some archeology to find out in which version we added this or that class or method.
On Thu, Nov 21, 2013 at 5:00 PM, Luke Daley <luke.da...@gradleware.com>wrote: > This would be a good thing to do when adding to the public API. > > It's kind of awkward to start this at an arbitrary point though. > > Begin forwarded message: > > *From: *Gradle <noreply.gra...@getsatisfaction.com> > *Subject: **New idea: @since for Gradle DSL/JavaDoc and GroovyDoc* > *Date: *20 November 2013 8:17:41 pm GMT > *To: *luke.da...@gradleware.com > > Gradle > > Spencer > Allain<http://forums.gradle.org/people/spencer_allain?utm_content=profile_link&utm_medium=email&utm_source=new_topic>just > shared this idea in > Gradle<http://forums.gradle.org/gradle?utm_content=company_link&utm_medium=email&utm_source=new_topic>: > > * @since for Gradle DSL/JavaDoc and GroovyDoc > <http://forums.gradle.org/gradle/topics/_since_for_gradle_dsl_javadoc_and_groovydoc?utm_content=topic_link&utm_medium=email&utm_source=new_topic> > * > It would be great if the DSL and the linked javadoc/groovydoc had @since > or equivalent tags corresponding to when properties and methods were added. > It could even be applied to plugins, and maybe there could be some > @incubating-since notation, so you can get a quick feel as to how long > something has been incubating. > > This information can be dug up by looking through the old release notes > and trolling through the documentation to see when something appeared (or > even digging into the github source to find out revision numbers there), > but it's much more cumbersome to do this. > > -Spencer > > Reply<http://forums.gradle.org/gradle/topics/_since_for_gradle_dsl_javadoc_and_groovydoc?do=reply&utm_content=reply_link&utm_medium=email&utm_source=new_topic> > > View topic in Manage > Workspace<https://console.getsatisfaction.com/manage/77943/conversations/5788912> > > Notify me when people > reply<http://forums.gradle.org/gradle/topics/_since_for_gradle_dsl_javadoc_and_groovydoc/follow?utm_content=follow_link&utm_medium=email&utm_source=new_topic> > > This message sent from the Gradle community on Get Satisfaction. > To unsubscribe or change your email settings, click > here<http://forums.gradle.org/me/notifications?utm_medium=email&utm_source=new_topic>. > Don't reply directly to this email. > > Create a customer > community<http://forums.gradle.org/plans?utm_campaign=create_a_community&utm_content=create1&utm_medium=email&utm_source=notifications_email>for > your company at > GetSatisfaction.com. > > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > -- Guillaume Laforge Groovy Project Manager Pivotal, Inc. Blog: http://glaforge.appspot.com/ Social: @glaforge <http://twitter.com/glaforge> / Google+<https://plus.google.com/u/0/114130972232398734985/posts>
