tools to manage Maven artifacts and deployment

 The Wagon project defines a simple API for transferring resources
 (artifacts) to and from repositories. The word repository is used in this
 context as it is commonly used in Maven and means a storage of artifacts.
 .
 It is also used to deploy the Maven generated site to a server.
 .
 This package contains the following Jars:
 .
  wagon-file
    Implementation of Wagon provider for File system access.
  wagon-ftp
    Implementation of Wagon provider for FTP access.
  wagon-http
    Implementation of Wagon provider for HTTP access.
  wagon-http-lightweight
    Implementation of Wagon provider for HTTP access. It uses standard
    JDK classes as lower lever layer.
    It enables Maven to use remote repositories stored in HTTP servers.
    It doesn't allow deployment.
  wagon-http-shared
    This package is a shared Library for the wagon-http, and
    wagon-http-lightweight wagon providers
  wagon-scm
    Implementation of Wagon provider for Source Control access.
    Gets and puts artifacts using a Source Control Management system.
  wagon-ssh
    Implementation of Wagon provider for SCP and SFTP access.
    It enables Maven to deploy artifacts and sites to SSH servers. It
    uses JSch (Java Secure Channel) as lower level layer.
  wagon-ssh-common
    Implementation of Wagon provider for SCP and SFTP access. It
    enables Maven to deploy artifacts and sites to SSH servers.
    Getting files from SSH servers is not fully tested.
  wagon-ssh-external
    Implementation of Wagon provider for SSH servers access. It
    enables Maven to deploy artifacts and sites to SSH servers.
    It uses an external SSH program that has to be already installed
    in the system. Getting files from SSH servers is not fully tested.
  wagon-webdav-jackrabbit
    Implementation of Wagon provider for WebDAV access.
    It uses the Apache JackRabbit library for WebDAV access.