Skip to content

Commit

Permalink
Better explanation of what's going on.
Browse files Browse the repository at this point in the history
  • Loading branch information
d6y committed Feb 17, 2012
1 parent 455fae8 commit 9a1426e
Showing 1 changed file with 17 additions and 7 deletions.
24 changes: 17 additions & 7 deletions README.md
Expand Up @@ -3,23 +3,33 @@ Build all External Lift Modules

This SBT project aims to build and publish all external Lift Modules against a specified version of Lift.

The purpose is to be able to change just this build when a new Lift version becomes available, and then this build will compile, package and publish external Lift modules without further intervention.
The purpose is to be able to change just this build when a new Lift version becomes available, and then this build will compile, package and publish external Lift modules without further intervention. At the same time, individual external Lift modules should still be able to do whatever they want to do on their schedule.


The Plan
---------

* List participating external modules in this build
* Ensure participating external modules use a common SBT `SettingKey` for the liftVersion, so that this build can jump in and change that value.
* Specify the latest Lift version in this build
* Build all participating modules using the version of Lift specified in this build.
* Build via Jenkins and email on error/warning.
* Publish successful builds into the external modules repo.

Status
------

* External modules and Lift version is defined in `project/LiftModulesBuildAll.scala`
* The Google Analytics module has been modified to be compatible with this (i.e., it uses the `liftVersion` Setting)
* publish does the right thing, but we have no control over where the output JAR is written.
* Waiting on SBT 0.12 to allow us to set staging directory [implemented by the fix to SSBT issue #331](https://github.com/harrah/xsbt/issues/331)
* The Google Analytics module [has been modified](https://github.com/d6y/liftmodules-googleanalytics/commit/8eb5db84b8b2ae346ca437a89449cb0d7478e03b) to be compatible with this (i.e., it uses the `liftVersion` Setting)
* package does the right thing, but we have no control over where the output JAR is written.
* -> Waiting on SBT 0.12 to allow us to set staging directory [implemented by the fix to SBT issue #331](https://github.com/harrah/xsbt/issues/331)

TO DO
-----

* Support publication
* Support publication into repo (trivial)
* Support building and publishing SNAPSHOTS
* Set up on Jenkins
* Communicate to Lift mailing list
* Set up on Jenkins (trivial)
* Talk to Lift team about triggering build for SNAPSHOT


Expand Down

0 comments on commit 9a1426e

Please sign in to comment.