ralph.goers @dslextreme.com wrote > > The part I'm struggling with is that if these are annotations vs just > javadoc tags then I would expect some kind of either compile time or > runtime behavior (or both). It seems that you are proposing javadoc tags > instead? If not what behavior would the annotations cause? > I'm not versed enough in Javadoc but I believe annotation carry more processing "power". The information can remain in the executable and allow post build analysis. To feed a clirr report, it seems we'd need to introspect the classes/methods to find those @internal. One could even dream of a -your favorite IDE here- plugin that warns you when using one of those. If there is an easy / easier practical solution that could serve the same purpose, I'm all for it!
-- View this message in context: http://apache-commons.680414.n4.nabble.com/RELEASE-PROCESS-Stability-versus-usability-tp4150322p4156415.html Sent from the Commons - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
