Closed Ulathar closed 2 years ago
Greetings!
Thank you a lot for the feedback, dankeschoen! On the concerns:
1) Libraries
We have provided FAT Jars including everything, here on GitHub.
Although we will commit a Gradle
build soonest.
2) On the Windows Paths
Point taken, I have never used Windows in my life but I will try to get a VMWare and test and adjust where necessary.
Give me 1-2 days please. Cheers
Oh I am not asking / demanding anything, was able to run some test migrations using my Raspberry Pi. So Windows Support would be a bonus, but thanks for your efforts and quick response ;-)!
The release v1.1 H2MigrationTool.jar seems not a FAT jar, right? Just make sure I don't missed anything.
Greetings Herb.
https://github.com/manticore-projects/H2MigrationTool/releases/download/1.1/H2MigrationTool.jar should contain everything (="Fat Jar"). What exactly is not working please or missing?
Using open jdk 11.0.2 Run: java -jar H2MigrationTool.jar Will get
Error: Unable to initialize main class com.manticore.h2.H2MigrationTool
Caused by: java.lang.NoClassDefFoundError: org/apache/commons/cli/ParseException
Sorry, I will have to fix that of course.
Thanks again for reporting, I have fixed that with release 1.2
Hey there,
just stumbeled across this tool and tried to give it a try but had some obsticales to overcome: To be able to execute the released JAR I had to lookup required dependencys in the jars manifest first and provide those jars alongside the main jar in /lib. No big deal, just wanted to point that one out (maybe add it to the readme?). Required libs which needs to be provided at runtime seem to be:
As soon as those are present the Tool runs fine (UI shows up and/or you can use the cli).
But after that I noticed that no matter what i try the tool fails right after the export step when it tries to create the new h2 Database from the generated .sql script. It looks like the jdbc paths are build wrong when running on a Windows maschine: (the problem here is the Drive letter followed by the ':'):
So I took a quick look into the code and found two relevant occurences of "driver.connect(...)" in H2MigrationTool.java that look like this:
In order to work properly with Windows filepaths something like this should work (using such connection strings in my own tool as well):
Bringing me to the next point: I tried to change those code parts accordingly and rebuild it locally on my machine using the provided build.xml file but can't get it to build either because of some absolute paths in the whole build xmls pointing to specific local paths and missing ClassPath configurations (those libs again mentioned above).
All in all very nice idea but does not seem to work poperly (yet) on Windows maschines unless I overlooked something.