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