No description provided.
It also depends on h2
Both should be test dependencies
Imported from Assembla: http://www.assembla.com/spaces/liftweb/tickets/1181
Currently they are in runtime scope, which means they aren't really compile time dependency. Having them in runtime is meant to be a hint for the downstream libraries and apps.
Just curious, are they affecting the way apps see these runtime dependencies?
I just checked and whatI notice is that if you depend on mapper, but do not depend on h2 nor derby, derby will be downloaded and be in the classpath for my project.
After doing a sbt package, I then looked inside the war and I found the derby jar is there, as well as h2.
Fixed #1181 - lift-mapper depends on derby