Move common dependencies from lift-base, lift-persistence, etc. into lift-parent
Obviously there are common dependencies like scala-library and junit that every module needs. Currently these are repeatedly defined in the aggregators lift-base, lift-persistence, etc.
Additionally many of these dependency declarations define the scope, what is not necessary, because the default scope is defined in the dependencyManagement section of lift-parent.
I suggest to move the common dependencies to lift-parent.
Additionally many of these dependency declarations define the scope, what is not necessary, because the default scope is defined in the dependencyManagement section of lift-parent.
I suggest to move the common dependencies to lift-parent.
Leave a comment
on 2010-04-03 18:20 *
By Heiko Seeberger
Required documentation set to None
Description changed from Obviously there are common ... to Obviously there are common ...
(In revision:bda792aa7f02ad54dabf48dcbf632bd799c13f89) - Pull up common dependency description from respective modules to lift-parent
- Remove multiple scope definition for dependencies. Close #421
- Update AMQP dependencies to use RabbitMQ 1.7.2 and remove reference to nexus.griddynamics.net. Close #450
Branch: master
- Remove multiple scope definition for dependencies. Close #421
- Update AMQP dependencies to use RabbitMQ 1.7.2 and remove reference to nexus.griddynamics.net. Close #450
Branch: master