Apache OpenOffice (AOO) Bugzilla – Issue 105719
Exporting BASIC library as extension creates zero sized file
Last modified: 2009-12-15 09:29:26 UTC
Automated test: framework/optional/f_basic_package_export_import.bas Reproduction (from autotest) Open one single writer document, modify it global::tools::includes::optional::t_docfuncs.inc::hInitSingleDoc::A single unchanged writer document is open Open another document, we want to have two to see that they both appear in the BASIC organizer Open BASIC organizer Select the second document Click <Manage...> Go to the libraries tabpage hSelectBasicObjectOrganizerTab::Libraries-Tab is open Select the document at pos. 4 Verify that the correct document has been selected Click <New...> Name the new library: tBasicExport The correct library is selected in the libraries list Click <Edit...> Insert a test macro (something simple, e.g. a messagebox hGetAccel::Enter with option: SelectAll hGetAccel::Requested accelerator: <mod1 a> for language: en-US hDeleteMacro::Using Accel: <mod1 a> hIsEditWindowEmpty::yes hInsertMacroFromFile::Inserted macro: tBasicExport Close the BASIC IDE Open the BASIC organizer Select the work document Manage... Libraries tab hSelectBasicObjectOrganizerTab::Libraries-Tab is open Select the new library Export the package, close the document afterwards Select to export as package Save the file, automatic filename extension must be checked Close libraires tabpage Close BASIC organizer Close all files
Adjusted priority to P2 - data loss, added kwd "regression"
Not reproducible in fwk117, so obviously a duplicate of the issue fixed there. ab->jsk: Please also check on m61. *** This issue has been marked as a duplicate of 105082 ***
duplicate -> closed
This problem is new with OOo320m4 whreas fwk117 has been integrated into OOo320m1. So this is neiteher fixed nor duplicate. Reopen.
Re-evaluating issue on OOo320 and DEV300... Please take no action until completed.
In OOo320m5 the problem persists. The .oxt file is created with zero size.
*** Issue 107039 has been marked as a duplicate of this issue. ***
sorry for the dup ;-)
ab->mav: As discussed...
This bug ( the second reincarnation ) is caused by the changes in the package component. The problem is that the package is no more able to overwrite the file it is based on.
fixed in fwk129
mav->jsk: Please verify the issue.
Automated test has been adjusted to be more timing tolerant (we had some "slot is already being executed" warnings). Fixed the filesize for the extension produced by this test and re- enabled the warning if it does not fit. Updated wording ("package" is now "extension") to reflect what is written in the UI. We're printing out the fully qualified path to the generated extension for easier debugging. The test claims all is well (Linux), running additional extension tests just to be sure, adding a few tests from the BASIC group as well.
svn commit -m "fwk129: #i105719 - Fixed file size, wording and timing" Sende framework/optional/includes/basic_package_export.inc Übertrage Daten . Revision 277700 übertragen.
Close