Well moving the rules to common file will defeat the purpose of the split, especially when more and more rules will use unification...
I looked in the code a bit more and it looks that we disable validation when we load rules in LT, that's why loading in run-time is working fine, and then I guess Java references the unifications that are already loaded. I'll keep looking for good solution, Andriy 2014-04-03 12:23 GMT-04:00 Daniel Naber <daniel.na...@languagetool.org>: > On 2014-04-03 01:12, Andriy Rysin wrote: > >> I guess we have two ways to go from here: adjust the tests to load >> files >> and keep them (I am not sure how easy it is - depends on how flexible >> our XMLValidator is) > > We're just using standard XML validation, I don't think there's much we > can do (other than catching that specific exception, which would be very > ugly). But not many rules are affected, what about moving those to > grammar.xml? (I know, that's not very elegant either). > > Regards > Daniel > > > ------------------------------------------------------------------------------ > _______________________________________________ > Languagetool-devel mailing list > Languagetool-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/languagetool-devel ------------------------------------------------------------------------------ _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
