Christoph Pickl - 2016-06-27

ok, so there are many weird things going on, about not being able to load the database because no proper handler is registered. the same with the lock service. seems as the ServiceLocator which comes with liquibase (which uses package scanning and stuff) is not working properly when wrapped in an EXE. it uses some resource/package scanning and this seems to be broke...

the launch4j.log file content:

Version:    3.8
CmdLine:    C:\dev\liquibase_launch4j_bug\liquibase_launch4j_bug\foobar.exe --l4j-debug
WOW64:      yes
Working dir:    C:\dev\liquibase_launch4j_bug\liquibase_launch4j_bug\.
64-bit search:  SOFTWARE\JavaSoft\Java Runtime Environment...
Check:      SOFTWARE\JavaSoft\Java Runtime Environment\1.8
Ignore:     1.8
Check:      SOFTWARE\JavaSoft\Java Runtime Environment\1.8.0_77
Check launcher: C:\Program Files\Java\jre1.8.0_77\bin\javaw.exe (OK)
Match:      1.8.0_77
Check:      SOFTWARE\JavaSoft\Java Runtime Environment\1.8.0_91
Check launcher: C:\Program Files\Java\jre_bsc\bin\javaw.exe (OK)
Match:      1.8.0_91
64-bit search:  SOFTWARE\JavaSoft\Java Development Kit...
Runtime used:   1.8.0_91 (64-bit)
Launcher:   C:\Program Files\Java\jre_bsc\bin\javaw.exe
Launcher args:  -jar "C:\dev\liquibase_launch4j_bug\liquibase_launch4j_bug\foobar.exe"
Args length:    81/32768 chars
Exit code:  0
 

Last edit: Christoph Pickl 2016-06-27