Once we have Java 9 as our minimum, we can use the `since` and `forRemoval` Deprecated attributes and that will allow us to make such deprecations a little clearer.
On Sun, Mar 24, 2019 at 12:26 PM Paul King <pa...@asert.com.au> wrote: > If you want to deprecate now and not in the future, I think that would > still warrant a question on the users list. > People often feel compelled to get rid of the deprecation warnings and > that still means two versions of their libraries would be required. > I'd be inclined to wait until Groovy 4 for deprecation. > > > On Sun, Mar 24, 2019 at 11:05 AM Daniel.Sun <sun...@apache.org> wrote: > >> OK. Let's add an alias method `accept` and mark method `visit` deprecated. >> >> Cheers, >> Daniel.Sun >> >> >> >> >> ----- >> Apache Groovy committer >> Blog: http://blog.sunlan.me >> Twitter: @daniel_sun >> >> -- >> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html >> >
