Hi, we have now about 30 methods in our code that are deprecated. I suggest removing them all for the next release. Why now? Well, with our 3-month release schedule version numbers don't play a role, so it doesn't seem to make sense to wait for LT 3.0. The CHANGES.txt file will then recommend updating to 2.5 first (and fix the deprecation warnings) before updating to 2.6. Of course, this is only relevant to developers using the Java API. Neither end users nor users of the HTTP API will be affected.
Any objections? BTW, I see WordFastTMReader is not used anywhere in our code. Is it useful to keep it? Also, the Demo language is part of our core package, although it's basically only used for tests. Is there any reason not to move it (and its rules etc.) to the test package? Regards Daniel ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
