Closed GoogleCodeExporter closed 9 years ago
That happens when both db.jar and je.jar are included in the same classpath. It
must be one or the other. This is because both implementations use the same
package and class names. Unfortunately, there's no way around this and it's not
a HGDB problem.
Original comment by borislav...@gmail.com
on 5 Jul 2012 at 1:36
Original issue reported on code.google.com by
Ingvar.Bogdahn
on 4 Jul 2012 at 8:54