Hello Russel,
as a maven addict I stumbled upon multiple java runtime ... too many times.
(release tag limit only your compiling classes, root cause is a java 8
running your pgms against a java9 derby lib).
In order to get repeatable builds I use (but it's a very personal
choice) maven
I'm using JDK 11, but it's true that I have the language options
narrowed to Java 8 (lambda, type annotations, etc.). However, that's in
IntelliJ IDEA. There's a sort of wall between how things are done up to
Java 8 and how they're done in the world that comes after. It's time to
cross that
It seems to me that you're running test with java 8 ( 50 => 6, 51 => 7,
52 => 8, ...).
But Derby requires java 9.
Bye,
Davide Grandi
On 26/06/2020 17:11, Russell Bateman wrote:
I get UnsupportedClassVersionErrorin each case. Here's what that looks
like:
I get UnsupportedClassVersionErrorin each case. Here's what that looks like:
testDirectlyToDerby(com.imatsolutions.database.ApacheDerbyTest)
java.lang.UnsupportedClassVersionError:
*org/apache/derby/impl/jdbc/EmbedConnection* has been compiled by a
more recent version of the Java
1) Do you have a stack trace showing what class can't be resolved?
2) What happens if you do a Class.forName() on the following classes,
which live, respectively, in derby.jar, derbyshared.jar, and derbytools.jar:
org.apache.derby.impl.jdbc.EmbedConnection
Oops. I spoke too soon. I still had my JUnit tests @Ignore'd. It doesn't
work yet. I still get "no suitable driver." I added derbytools too, but
that made no difference. Further thoughts?
On 6/25/20 5:01 PM, Russell Bateman wrote:
Thank you; that's very kind. It now works. (I'm not using
Thank you; that's very kind. It now works. (I'm not using DataSources
for now.) I greatly appreciate your help.
Best regards,
Russ
On 6/25/20 4:48 PM, Rick Hillegas wrote:
The 10.15 family of releases introduced a JPMS modularization of
Derby. That re-factored the code a bit. You will need to
The 10.15 family of releases introduced a JPMS modularization of Derby.
That re-factored the code a bit. You will need to add derbyshared.jar to
the classpath and build dependencies. If you are using DataSources, then
you will also need to add derbytools.jar. Please see the detailed
release
