The current version of the maven buildnumber plugin does not yet support the git scm backend. This makes it harder to get the git sha for the current build (often a snapshot build) into the MANIFEST.MF file.
Let's look at using the exec plugin as a workaround.
This is based on http://www.versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/
This is a work in progress/idea dump right now - any suggestions/improvements - please do leave a comment ;)
I have quite a few sites that are using drupal. I know I could go the route of a multisite install (I've done it before) - but I found that the requirement of upgrading all sites simultaneously was a bit too hard. However - upgrading everything by hand for each site is also poor.
With the backported git 1.6 packages installed (see Backport git 1.6 for debian) - to add mailing lists for commits/tags:
cd src/<project>.git/hooks ln -s /usr/share/doc/git-core/contrib/hooks/post-receive-email post-receive git config --add hooks.mailinglist "development@mailhost.tld" git config --add hooks.announcelist "announce@mailhost.tld" git config --add hooks.envelopesender "from_addr@host.tld"
Note that /usr/share/doc/git-core/contrib/hooks/post-receive-email must be executable - chmod a+x if you need to.
Using git for handling CVS checkouts for drupal contrib:
Details are on Maintaining a Drupal module using Git
For Mac OSX users you will need cvsps (fink install cvsps for example).
Useful alias for your .gitconfig:
drupalcontribcvs = !sh -c 'git cvsimport -p x -v -d:pserver:anonymous@cvs.drupal.org:/cvs/drupal-contrib contributions/modules/$0'
This allows you to call
git drupalcontribcvs <modulename>
git 1.6 is available in debian experimental. I want to use it under debian stable (etch).
Let's backport it.
Kudos to Steve Kemp for walking me through this.