sakaiproject/sparsemapcontent — pull request #49 by raydavis (2012-04-06 18:23:02+00:00)
Title: Sparse 176

The point of this change is to keep a vanilla build of SparseMapContent building the artifacts required by a vanilla build of Nakamura. As a side-effect, it reorganizes project directories to match the standard Maven set-up, with the parent POM at the top of the tree and artifact-producing modules in subdirectories.

It's packaged as three commits. If you decide to merge, DO NOT SQUASH! Git's rename/move logic is utterly befuddled by a single commit which moves file A somewhere and also moves file B into file A's old path.

https://jira.sakaiproject.org/browse/SPARSE-176