lift-mapper depends on derby #1181

merged 1 commit into from Jul 1, 2012


None yet

5 participants


No description provided.


It also depends on h2

Both should be test dependencies

@indrajitr indrajitr was assigned Mar 1, 2012

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.

@fmpwizard fmpwizard closed this in 21ac622 Jul 1, 2012
@fmpwizard fmpwizard reopened this Jul 1, 2012
@dpp dpp merged commit f6bdd84 into master Jul 1, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment