See also Alexandre's comments at http://java.dzone.com/tips/using-maven-repository-kenai

There are some things to fix:

1. The CMR doesn't allow to publish snapshots.
2. The groupId must resolve to a DNS domain I own
3. There must be no dependencies on artifacts not on the CMR. At the moment, there are two:
3a. The Wagon extension for deploying to SVN repos is not on the CMR. We still need it because the idea is to publish releases on the CMR and snapshots on Tidalwave Repo.
3b. There is a test dependency on TheseFoolishThings, that is on my repository.

Problem 3b should be easy, as I can publish TheseFoolishThings to the CMR.

We need to decide final names for artifactIds before polluting the CMR!

Problem 3a is solved, as Alexandro hinted that v1.9 of the Wagon stuff is on the CMR.

This means that problem 3 is solved, and we can continue publishing snapshots on Tidalwave repo; problem 1 is solved too.

For problem 2, I don't like the suggestion of using com.kenai.betterbeansbinding for the groupId. I don't want to put the forge name in the project. But it.tidalwave.betterbeansbinding would be probably ok. Need to ask to the CMR staff.

Maybe that could be just (org.)betterbeansbinding instead of it.tidalwave.betterbeansbinding or com.kenai.betterbeansbinding?

It is not possible: to be able to publish to the CMR, it must be a domain name that I own / I'm maintaining, etc... Thus, the only solutions are com.kenai.* and it.tidalwave.*.

Done.