**IMPORTANT** **BREAKING CHANGES** lift-core is deprecated
Indrajit Raychaudhuri
If your project has dependency on lift-core, this is important for you!
lift-core stands deprecated and Lift 2.0-M2 would be the penultimate
milestone with support for lift-core. Subsequently (after the milestone
2.0-M3) it would be unsupported.
lift-core is a 'meta' module that can be added as a dependency to a Lift
based application to pull in all the Lift modules. The initial purpose
of having single dependency on this 'meta' module in the application was
to conveniently serve as a singular configuration point in a Lift based
application.
However, this comes for a cost. Since lift-core downloads and enforces
bundling all the Lift modules (irrespective of whether the project needs
it), adding this as the dependency slows down things for a standard Lift
application that doesn't need all the additional modules. Further, this
makes the generated application war much larger than necessary.
Going forward, just discontinue using lift-core in your project and for
alternative(s), follow these general guidelines:
1. If you are using any of the persistence modules (lift-mapper,
lift-jpa, lift-record), just have the respective persistence module as
dependency. You *do not* need to add any of the other base modules
(lift-common, lift-actor, lift-json, lift-util, lift-webkit) as dependency.
2. If you are not using the persistence module (possibly because your
app doesn't need such support), just including lift-webkit should suffice.
3. Additionally, if you are using any of the special purpose modules
(from lift-modules), add that to the list of dependencies in addition to
the ones added in #1 or #2 above.
In all the above cases, the additional dependencies necessary (and just
the necessary ones) for the respective modules would be pulled
transitively in your project automatically.
This would make your application lighter by having more precise
dependency map. And that's a good thing!
Cheers,
Indrajit