[api-dev] XPaketManager.removePackage changes
Hi all, I have a little question conserning the method css.deployment.XPaketManager.removePackage(...). In OpenOffice.org 2.3 this method takes 4 parameters. In OpenOffice.org 2.2.1 (Debian) it takes 3 parameters. Is this correct? If yes, is the 2.2.1 API of this class undocumented? Greetings, Tobias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] XPaketManager.removePackage changes
Tobias Krais wrote: Hi all, I have a little question conserning the method css.deployment.XPaketManager.removePackage(...). In OpenOffice.org 2.3 this method takes 4 parameters. In OpenOffice.org 2.2.1 (Debian) it takes 3 parameters. Is this correct? If yes, is the 2.2.1 API of this class undocumented? i assume you mean XPackageManager ;-) Anyway this API is unpublished and intended to be used internally only. But of course important is here that it is unpublished and that means that it can change and users have to be careful when using this API. I know that it is not really satisfying but that is the situation today. Juergen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] XPaketManager.removePackage changes
Hi Juergen i assume you mean XPackageManager ;-) Anyway this API is unpublished and intended to be used internally only. But of course important is here that it is unpublished and that means that it can change and users have to be careful when using this API. I know that it is not really satisfying but that is the situation today. Is it planned to make it public one day ? Laurent -- Laurent Godard [EMAIL PROTECTED] - Ingénierie OpenOffice.org - http://www.indesko.com Nuxeo Enterprise Content Management http://www.nuxeo.com - http://www.nuxeo.org Livre Programmation OpenOffice.org, Eyrolles 2004-2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] XPaketManager.removePackage changes
Laurent Godard wrote: Hi Juergen i assume you mean XPackageManager ;-) Anyway this API is unpublished and intended to be used internally only. But of course important is here that it is unpublished and that means that it can change and users have to be careful when using this API. I know that it is not really satisfying but that is the situation today. Is it planned to make it public one day ? It doesn't matter because it's always possible to have unpublished API's that are primary intended for private usage and that remain unpublished. General recommendation is to publish API's after 1-2 releases, especially when they provide some new typical service provider functionality. Juergen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
