Jdbcslim tests are failing on the H2 driver when using maven about jdbcslim HOT 9 CLOSED

If you update your POM file described in PR #20 specific file https://github.com/six42/jdbcslim/pull/20/files#diff-600376dffeb79835ede4a0b285078036 and execute the commands described in specific https://github.com/six42/jdbcslim/pull/20/files#diff-04c6e90faac2675aa89e2176d2eec7d8 file, then it should work.

from jdbcslim.

Did you do any manual action (i.e. edit plugin.properties) to get the jdbcAuthenticator?
I don't believe I had that, and the problem with Java 9+ only occurs with plugins...

from jdbcslim.

I fixed the merge issue on #20

I'm not currently using jdbcslim, and when I was I just added it as a dependency to my own fitnesse project and ran the wiki and my tests from there.

Can you elaborate on what MojoExecutionException you got exactly (message and stack trace)?

from jdbcslim.

I think I see what the problem is: you are running with Java 10.
The fitnesse version used in the pom.xml for jdbcslim does not yet support running on anything above Java 8.
Can you try updating the version in the pom.xml to 20190224?

@six42 Can you upgrade to a more recent version (anything above 20180127 should work, I recommend 20190224, of course)?

from jdbcslim.

Maybe it is not Java 10. I just tried exec:exec locally with Java 8 and 11 and both worked

from jdbcslim.

Thanks @fhoeben for your PR #20.
I just merged it.

Also updated ReadMe. Just noticed that it didn't mentioned gradle as build option at all.

from jdbcslim.

@Unforgettable631 Thanks! I've just been battling along with issues here and replacing the content of my pom.xml with that referenced in PR #20 just got me a proper build. Sorry I was a bit premature in my excitement; turns out I was able to compile jdbcslim.jar and get build success out of mvn clean package but when I run mvn exec:exec I get a MojoExecutionException :(

Unfortunately my attempts to get jdbcslim running are by necessity part of a time-limited experiment, so I'm not going to be able to focus on it for much longer. Happy to run any experiments in my own time to help investigate the issue if you're having trouble replicating it.

@six42 @fhoeben any chance we can get that PR actioned so others don't have the same struggle?

Please note I started with the Ant instructions and got no joy from them, so was trying Maven.

from jdbcslim.

Thanks @fhoeben I've just generated the output for you, please find them attached.

My steps to generate these:

1. Blew away my changes back to the state of master.
2. Replaced pom.xml with content from pom.xml on your PR.
3. Ran mvn_clean_package and grabbed stack trace.
4. Ran mvd exec:exec (then again with -e & -X switches) and grabbed stack trace for the whole bunch.

Hope that helps :)

Files
mvn_clean_package.stacktrace.txt
mvn_exec-exec.stacktrace.txt

from jdbcslim.

Thanks for the suggestion mate, gave it a try just in case but actually mvn clean package failed after amending the fitnesse.version, have attached the stack trace in case it's useful, see mvn_clean_package-POM-20190224.txt.

You raise a good point, I had created a plugins.properties file when trying to understand my issue and going through the documentation, and that wasn't tracked in my branch so discarding all my changes didn't remove it!
Manually removed plugins.properties and tried again with the edited POM still had no joy (see mvn_clean_package-POM-20190224_plugins.properties_removed.txt if you like), but then reverting back to the PR #20 POM without plugins.properties present (see
mvn_clean_package-just_plugins.properties_removed.txt and
mvn_exec-exec.stacktrace-just_plugins.properties_removed.txt for trace) which looks pretty good!

Unfortunately I'm going to struggle to find time to make any actual attempt to use this in anger today, the tyranny of prioritization being what it is, but I will make an effort to do so either at lunch or after work and report back :)

from jdbcslim.