Ooh, that is super-tempting. Not just IDEs: other code checkers will also start complaining (FindBugs?). Changing the API will let start on the path to better code quality through automatic tools.
We should discuss at Tuesday's meeting. If we do this, we should deprecate dispose() for a least one release cycle. Kind regards, Ben. On 11/01/16 12:25, Jody Garnett wrote: > Got a question, is it worth an api change dispose() --> close() to avoid > the IDE errors? -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
