Inconsistent artifact deployment method across plugins

[Charles Blaxland <ch...@EB2-International.com>]

Hi,

The various maven plugins are inconsistent in the way they deploy 
artifacts to the remote repository.  They use, variously, 
artifact:deploy or deply:artifact, for example:

war:deploy  -> artifact:deploy
ejb:deploy  -> artifact:deploy
jar:deploy  -> deploy:artifact
dist:deploy -> deploy:artifact

Is there any particular reason for this?  It'd be great to see all 
plugins standardized to use artifact:deploy to provide more flexibility 
in choosing the deployment method (eg: ftp).  We're running Windows 
exclusively here, so simply using FTP is a lot less pain than having to 
install and configure ssh servers/clients.

Along the same lines, an ftp option for site:deploy would be nice.

Cheers,
Charles


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