Question

Note: I am not asking how to use Google Code’s SVN repo as a Maven repo 🙂

I’m looking for the simplest / most reliable way to automate uploading the built artifacts of a Maven project to a Google Code ‘Downloads’ tab.

I’ve found 4 different Google Code Maven plugins that claim to do this, but would appreciate any advice on evaluating them as fit-for-purpose, because they all seem to be in various states of inactivity.

1. maven-googlecode-plugin (Last commit: Sept 2009. Latest version: 0.0.1-SNAPSHOT)
2. gcupload-maven-plugin (Last commit: Jan 2009. Latest version: 0.9)
3. maven-gcu-plugin (Last commit: Oct 2010. Latest version: 1.1)
4. maven-googlecode (Last commit: Feb 2008. Latest version: 2.0, but labelled ‘test’)

In addition to these ‘level of activity’ clues, some of them offer their releases on the ‘Downloads’ tabs, which might be a good sign from an ‘eat your own dogfood’ viewpoint; but as these are supposed to be Maven plugins, having them available in Maven Central might inspire more confidence.

Anyone care to comment (perhaps even the owners / committers of these projects) ?

Thanks!

---

Update:

I have test-driven each one of these in turn and could not get any of them to work as advertised.

Two of them are still configured to upload to a Google Code URL ending in /files, whilst another claimed to work and reported success, but the artifacts did not appear in the ‘Downloads’ tab. With the last one there appeared to be no released code which could be referenced as a Maven plugin.

I have since emailed each of the project committers to see what can be done.

Answer 1

If you are not averse to looking beyond maven plugins, google code has a SciptedUploads documentation, which seems to provide a python script and an ant task for doing this.

You may want to start reading the comments bottoms-up to see challenges using them, if any.

I got to this page by clicking on the link to “Create a New Download” for my google code project and clicking on the “Tip”.