#307
- Created on2010-01-27 07:39
- Reported by
- StatusFixed
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Streamline JDBC library dependencies
Currently, the JDBC library dependencies are scattered all over the places in the codebase.
We need to fold them as dependencyManagement up in the canonical project-parent pom and refer to them selectively from the modules that need them. less dependency count = faster and leaner build :)
While at this, update the versions of some of the jars. This version update should not affect applications based on Lift because they are in the runtime scope and marked optional=true (and thus aren't transitive)
We need to fold them as dependencyManagement up in the canonical project-parent pom and refer to them selectively from the modules that need them. less dependency count = faster and leaner build :)
While at this, update the versions of some of the jars. This version update should not affect applications based on Lift because they are in the runtime scope and marked optional=true (and thus aren't transitive)
Leave a comment
on 2010-02-06 14:52 *
By github.importer
Imported from GitHub: http://github.com/dpp/liftweb/issues/307/find
DB driver dependencies for persistence modules should not be transitive.
It should either be in 'runtime' scope with optional=true or 'test' scope.
Recommend 'test' scope for H2 and Derby drivers necessary for test cases in lift-record, lift-mapper.
It should either be in 'runtime' scope with optional=true or 'test' scope.
Recommend 'test' scope for H2 and Derby drivers necessary for test cases in lift-record, lift-mapper.
