> I would be disappointed by this move - language identifier is an > important component in Nutch. Now the mere fact that it's bundled with > Nutch encourages its proper maintenance. If there is enough drive in > terms of willingness and long-term commitment it would make sense to > move it to a separate project on its own (or maybe as a part of Jakarta > Commons), but moving it into a catch-all purely optional category like > Lucene contrib would increase risks that it slides into oblivion...
Ok, Andrzej, I really understand your meaning. But more and more people are contacting me directly in order to use the language-identifier, but not as a nutch plugin, simply as a standalone library. They get confused when I explain them that they need the nutch jar in order to use the language-identifier. That's why I would like to make it a standalone jar. A short-term solutions could be to move the core classes (which have no dependencies on nutch) to a new lib-plugin (lib-lang for instance and adding a dependecy to this plugin in the language-identifier), so that this code could be used as a standalone lib. Are you ok, with such changes? Jérôme -- http://motrech.free.fr/ http://www.frutch.org/
