Apache OpenOffice (AOO) Bugzilla – Issue 93266
create_services_rdb failed - CannotRegisterImplementationException
Last modified: 2013-08-07 15:26:05 UTC
Fri Aug 29 12:26:54 2008 (02:06 min.) dmake: Error code 255, while making 'openoffice_uk.bsd' Running processes: 0 1 module(s): instsetoo_native need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /meow/ports/editors/openoffice.org-3-devel/work/DEV300_m29/instsetoo_native/util Attention: if you build and deliver the above module(s) you may prolongue your the build issuing command "build --from instsetoo_native" I'll attached the generated log-file (instsetoo_native/unxfbsdx.pro/OpenOffice/bsd/logging/uk/log_DEV300_uk.log).
Created attachment 56098 [details] DEV300_m29/instsetoo_native/unxfbsdx.pro/OpenOffice/bsd/logging/uk/log_DEV300_uk.log
Sorry, forgot to mention, what may be important here. Lucene's JAR on my system is external to OOo's build.
as I see from the log... you are building DEV300_m29 on amd64..
Trying to build m30, I get the same-looking exception in the en-US language... It does look like it has something to do with my Lucene JARs being external to the build, but the error message is woefully incomplete... Full log_DEV300_en-US.log will be attached.
Created attachment 56119 [details] Installer log log_DEV300_en-US.log
is -> jl: Please have a look at this CannotRegisterImplementationException during creation of services.rdb in packaging process. Perhaps you already know this?
@ab: as discussed.
ab->panbk: You've already applied your patch from i93294 and get this problem afterwards, right? No patch -> DEFECT, STARTED, 3.1
Next try to set STARTED
ab->panbk: This looks like a specific build problem as obviously the build succeeds on other machines/platforms. I don't even know how I should reproduce it. Does it still occur at all on newer versions? Please check again.
= I don't even know how I should reproduce it. Try building relying on SYSTEM_LUCENE (and with the OOo's bundled lucene/ subdirectory removed).
OOo 3.1 is released. Therefore the target of this issue is obsolete. Please recheck the issue and find a concrete target for this issue. Until this I set this issue to target 3.x.