1The extension build in this test uses an update information which is obtained
2through a http get request. That is the URL does not reference an update
3information file. Instead it invokes code on a webserver which returns the
4update information. The URL used in this example is:
5
6http://update.services.openoffice.org/ProductUpdateService/check.Update?product=extension&extensionid=org.openoffice.extensions.testarea.desktop.updateinfo&refresh=true
7
8The updateinfo.oxt in this directory has the version 1.0 and in the sub-directory "update is the version 2 of this extension. Version 1.0 is also available here
9/extensions/www/testarea/desktop/updateinfocreation/updateinfo.oxt
10and version 2.0 here
11/extensions/www/testarea/desktop/updateinfocreation/update/updateinfo.oxt
12
13Therefore they can be accessed through
14
15http://extensions.openoffice.org/testarea/desktop/updateinfocreation/updateinfo.oxt
16and
17http://extensions.openoffice.org/testarea/desktop/updateinfocreation/update/updateinfo.oxt
18
19The latter location (version 2.0) will also be referenced by the update information
20which are returned by the webserver.
21
22The build sub-directory contains the code of the extension (version 2.0) and can
23be build by calling dmake in this directory. The makefile uses the special macros:
24
25EXTUPDATEINFO_NAME=org.openoffice.extensions.testarea.desktop.updateinfo.update.xml
26EXTUPDATEINFO_SOURCE=description.xml
27EXTUPDATEINFO_URLS = http://extensions.openoffice.org/testarea/desktop/updateinfocreation/update/updateinfo.oxt
28
29This causes the generation of the update information file. This file could be
30directly references by the URL in the <update-information> of the description.xml.
31See also the Wiki entry at:
32https://wiki.openoffice.org/wiki/Creating_update_information_for_extensions
33This generated update information file can then be used by the webserver, when it
34sends back the requested update information. The update information file will be
35generated in the misc diretory of the output directory.
36
37The update information file needs to be copied into common.pro/pus.mxyz directory.
38The project mwsfinish will process the files in the pus directory.
39