Attached is the second patch which should close this issue and
As I already mentioned, velocity-dep-1.6-beta2.jar is now velocity-1.6-beta2-dep.jar all over the place(I thought is not a good idea to have velocity-1.6-beta2-dep.jar in Maven repositories and velocity-dep-1.6-beta2.jar in Velocity distribution archives).
Right now there are two tasks maven-install and maven-deploy which depends on release but a different integration can be made, depending on how a release will be performed now.
Also, digital signatures ca be deployed to, just add(of course files must be signed after release and before deploy) :
.jar.asc" type="jar" classifier="jar.asc"/> for every asc file.
If "maven.remote.repository" property exists a custom repository will be used(and not the one from Maven POM). Repository id is velocity.custom.repository and the following entry must be added in $USER/.m2/settings.xml to provide authentication information for this repository.
You can have a look at velocity-1.6-beta2 artifacts in my repository. Did several tests with my IDE and Maven and all artifacts(jar, source & javadoc) worked as it should.