ieb/sparsemapcontent — Issue #134: sparsemapcontent 1.3 tag binds to snapshot artifacts; org.sakaiproject.nakamura.core-1.3.jar missing from oss.sonatype.org
Author: arwhyte
Created: 2011-11-28 22:12:36+00:00
State: open

The sparsemapcontent-1.3 tag includes a number of snapshot bindings:

1. parent/pom.xml maven-sling-plugin 2.0.5-SNAPSHOT->2.0.6 (pull request submitted for issue #132).
2. The extension builder is versioned 0.1-SNAPSHOT. I'd release this and deploy it to oss.sonatype.org. Also the base pom is also missing a ; all child extension poms except milton do not list an explicit ). Specifying Maven coordinates explicitly in a pom I think a good thing.
3. The drivers/cassandra and drivers/postgress poms are each versioned SNAPSHOT.

On no. 2 above I'm happy to tweek the sparse master extension builder poms and issue a pull request to add an explicit for the various extension poms. My default assumption is that the equals org.sakaiproject.nakamura. But the for all the extensions except miltion is uk.co.tfd.sm.[extenstion_name] (e.g., uk.co.tfd.sm.app). Did you intend the groupId for these to equal uk.co.tfd or uk.co.tfd.sm or org.sakaiproject.nakamura.

Also, looking at the sonotype oss repo the org.sakaiproject.nakamura.core-1.3.jar is missing. Only the pom, sources jar and javadoc jars are deployed to the repo.