I'm using Sonatype's hosting to stage my releases and sometimes need to drop 
back.

It's annoying to have it deploy the site docs when they don't conform to the 
actual released-on-central latest version.

I can't see an argument to stop this.

I suppose I could deploy to some bogus location by default, such as a different 
directory in target, and then have a profile that I can use to manually deploy, 
but it seems silly.

Any ideas?

BTW, in general, I like the release plugin a lot. You folks have done very good 
work on it.

-K
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to