Hi, the problem is that the Java API has changed. So our extension that used the old API cannot find classes in new jars, and because of this fact you cannot uninstall it via the Extension Manager. Moreover, you cannot even specify the maximum allowed version for an extension (we wanted to do so), as this was introduced in 3.1, so it doesn't work for 3.0.0.
Probably another workaround would be to manually copy the old jar to the extension directory and add it to the classpath, then use unopkg to remove the extension. In Linux, this is probably easily scriptable. In Windows, I'm not so sure... If you have any other suggestions, we will be grateful. This is a limitation of the Extension infrastructure, actually. The required maximum version feature is already implemented so this is already fixed for future versions of OOo. Regards Marcin Dnia 28 stycznia 2009 12:49 Mathias Bauer <[email protected]> napisał(a): > Hi, > > can you explain more deeply what the exact problem is? Is it a general > problem in our extensions infrastructure? > > Regards, > Mathias > > Marcin Miłkowski wrote: > > > Hi William, > > > > I have just made a wiki page with instructions for users: > > > > http://languagetool.wikidot.com/removing-languagetool-0-9-5-from-openoffice-3-0-1 > > > > But this is not very user-friendly as data loss seems to be inevitable in > > many cases. I have no easy procedure for saving unaffected settings and > > templates. > > > > And yes, I should have mentioned that using a singleton is really > > important. Equally important is to make the main checking method > > synchronized, otherwise your checker might be not ready with previous check > > and get another query. This results with incorrect behavior. > > > > Regards > > Marcin > > > > Dnia 28 stycznia 2009 11:47 William Colen napisał(a): > > > >> Hi all, > >> > >> LanguageTool developers already pointed an issue that one must de-install > >> the Grammar Checker extension compatible with OOo 3.0.0 before upgrading to > >> OOo 3.0.1. I found the same issue with Cogroo. It looks like we can't > >> remove > >> the extension anymore in this case. > >> Does anybody know a user friendly procedure that we could point to the > >> users > >> if they have this problem? I'm sure it will happen a lot and they will not > >> be happy with loosing all their configurations and extensions. > >> > >> Thank you > >> William > >> > >> PS: Thank you Thomas and Marcin. I could fix Cogroo, it was an > >> initialization problem. I notice that Cogroo was not singleton. That is > >> what > >> happens when one start doing things without studding the homework! > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- > Mathias Bauer (mba) - Project Lead OpenOffice.org Writer > OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS > Please don't reply to "[email protected]". > I use it for the OOo lists and only rarely read other mails sent to it. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
