| Name : maven-deploy-plugin
| |
| Version : 2.7
| Vendor : jPackage project
|
| Release : 3.jpp6
| Date : 2012-06-16 20:42:47
|
| Group : Development/Libraries
| Source RPM : maven-deploy-plugin-2.7-3.jpp6.src.rpm
|
| Size : 0.02 MB
| |
| Packager : Ralph Apel < r_apel_r-apel_de>
| |
| Summary : Add artifacts to repository
|
Description :
The deploy plugin is primarily used during the deploy phase,
to add your artifact(s) to a remote repository for sharing
with other developers and projects. This is usually done in
an integration or release environment. It can also be used
to deploy a particular artifact (e.g. a third party jar
like Sun\'s non redistributable reference implementations).
As a repository contains more than the artifacts (POMs, the
metadata, MD5 and SHA1 hash files...), deploying means not
only copying the artifacts, but making sure all this
information is correctly updated. It\'s the reponsibility
of the deploy plugin.
To work, the deployment will require:
* information about the repository: its location, the
transport method used to access it (FTP, SCP, SFTP...) and
the optional user specific required account information
* information about the artifact(s): the group, artifact,
version, packaging, classifier...
* a deployer: a method to actually perform the deployment.
This can be implemented as a wagon transport (making it
cross-platform), or use a system specific method.
The information will be taken from the implied (or specified)
pom and from the command line. The settings.xml file may also
be parsed to retrieve user credentials.
|
RPM found in directory: /packages/linux-pbone/archive/www.jpackage.org/jpackage/6.0/generic/free/RPMS |
