[Building Sakai] sakai-2.9.x-all build broken

[Steve Swinsburg]

This is an interesting discussion as it directly relates to the usefulness of the indies projects. A question, why do you want to build the source of all indies? Unless you've modified them, you can just let Sakai deploy the binaries and then updates are as easy as changing the version in the master pom. 

The TCC will be talking about the indies, the -all branches, and a possible -all tag soon. 

Cheers
Steve

Sent from my iPhone

On 16/11/2012, at 2:37, David Adams <da1 at vt.edu> wrote:

> I'm not sure who to contact about this, but currently the sakai-2.9.x-all branch isn't building against a fresh maven repo, as the master pom's sakai.warehouse.version setting is 2.9.1-SNAPSHOT, but the warehouse pom's version is 2.9-SNAPSHOT. It was an easy fix, but probably something that should be tweaked.
> 
> Problems like this make me wonder: is there any reason there's not a sakai-2.9.0-all tag that includes the exact kernel and indie source code tags? The sakai-2.9.x-all branch is fine for development work, but for deployment, I think the release tag is a safer starting point, but lots of schools are, essentially, making their own sakai-2.9.0-all branch locally so that they can build all of the source, so it would save us a LOT of time if that were one of the artifacts generated by the release process.
> 
> -dave
> -- 
> David Adams
> Director, Learning Systems Integration and Support
> Virginia Tech Learning Technologies
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"