Return-Path: X-Original-To: apmail-maven-commits-archive@www.apache.org Delivered-To: apmail-maven-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D2FA4DDF3 for ; Mon, 3 Sep 2012 20:21:28 +0000 (UTC) Received: (qmail 65855 invoked by uid 500); 3 Sep 2012 20:21:28 -0000 Delivered-To: apmail-maven-commits-archive@maven.apache.org Received: (qmail 65798 invoked by uid 500); 3 Sep 2012 20:21:28 -0000 Mailing-List: contact commits-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list commits@maven.apache.org Received: (qmail 65785 invoked by uid 99); 3 Sep 2012 20:21:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2012 20:21:28 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Sep 2012 20:21:08 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id E81612388B45 for ; Mon, 3 Sep 2012 20:19:58 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r831044 [10/23] - in /websites/production/maventest/content/plugins/maven-install-plugin-2.4: ./ apidocs/ apidocs/class-use/ apidocs/org/ apidocs/org/apache/ apidocs/org/apache/maven/ apidocs/org/apache/maven/plugin/ apidocs/org/apache/mave... Date: Mon, 03 Sep 2012 20:19:51 -0000 To: commits@maven.apache.org From: olamy@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120903201958.E81612388B45@eris.apache.org> Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/distribution-management.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/distribution-management.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/distribution-management.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,226 @@ + + + + + Maven Install plugin - Project Distribution Management + + + + + + + + + + + + +
+ +
+
+
+

Overview

The following is the distribution management information used by this project.

Repository - apache.releases.https

https://repository.apache.org/service/local/staging/deploy/maven2

Snapshot Repository - apache.snapshots.https

https://repository.apache.org/content/repositories/snapshots

Site - apache.website

< p>scp://people.apache.org/www/maven.apache.org/plugins/maven-install-plugin/

+
+
+
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/distribution-management.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/distribution-management.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/custom-pom-installation.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/custom-pom-installation.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/custom-pom-installation.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,187 @@ + + + + + Maven Install plugin - Installing an artifact with a custom POM + + + + + + + + + + + + + + +
+ +
+
+
+

Installing an artifact with a custom POM

The Maven Install Plugin can include a pre-built custom POM with the artifact in the local repository. Just set the value of the pomFile parameter to the path of the custom POM.

mvn install:install-file -Dfile=path-to-your-artifact-jar -DpomFile=path-to-pom
+
+
+
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/custom-pom-installation.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/custom-pom-installation.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/generic-pom-generation.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/generic-pom-generation.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/generic-pom-generation.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,192 @@ + + + + + Maven Install plugin - Generating a generic POM + + + + + + + + + + + + + + +
+ +
+
+
+

Generating a generic POM

There are times when you do not have a POM for a 3rd party artifact. For instance, when installing a proprietary or commercial JAR into a repository. The Install Plugin can create a generic POM in this case which contains the minimal set of POM elements required by Maven, such as groupId, artifactId, version, packaging. You tell Maven to generate a POM by setting the generatePom parameter to true.

mvn install:install-file  -Dfile=path-to-your-artifact-jar \
+                          -DgroupId=your.groupId \
+                          -DartifactId=your-artifactId \
+                          -Dversion=version \
+                          -Dpackaging=jar \
+                          -DgeneratePom=true
+
+
+
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/generic-pom-generation.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/generic-pom-generation.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-checksums.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-checksums.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-checksums.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,192 @@ + + + + + Maven Install plugin - Creating artifact checksums + + + + + + + + + + + + + + +
+ +
+
+
+

Creating artifact checksums

The Install Plugin can create integrity checksums (MD5, SHA-1) for the artifacts during installation. Checksums are cryptographic hash functions and are used to check the integrity of the associated file. This can be activated by setting the createChecksum parameter to true.

In the install:install goal.

mvn install -DcreateChecksum=true

In the install:install-file goal.

mvn install:install-file  -Dfile=path-to-your-artifact-jar \
+                          -DgroupId=your.groupId \
+                          -DartifactId=your-artifactId \
+                          -Dversion=version \
+                          -Dpackaging=jar \
+                          -DcreateChecksum=true
+
+
+
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-checksums.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-checksums.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-secondary-artifacts.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-secondary-artifacts.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-secondary-artifacts.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,192 @@ + + + + + Maven Install plugin - Installing Secondary Artifacts + + + + + + + + + + + + + + +
+ +
+
+
+

Installing Secondary Artifacts

Sometimes you need to install secondary artifacts after the main artifact has been installed in your local repository. To install a secondary artifact you need to use the classifier parameter to classify the secondary artifact.

Let us assume that you want to install the sources for an old artifact, like commons-logging-1.0.3. The central repository only has the main artifact and a -javadoc artifact for that version. Package up the sources into a JAR file on your local disk and then run the following command:

mvn install:install-file  -Dfile=path-to-commons-logging-sources.jar \
+                          -DgroupId=commons-logging \
+                          -DartifactId=commons-logging \
+                          -Dversion=1.0.3 \
+                          -Dpackaging=jar \
+                          -Dclassifier=sources
+
+
+
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-secondary-artifacts.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/installing-secondary-artifacts.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/specific-local-repo.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/specific-local-repo.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/specific-local-repo.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,192 @@ + + + + + Maven Install plugin - Installing an artifact to a specific local repository path + + + + + + + + + + + + + + +
+ +
+
+
+

Installing an artifact to a specific local repository path

By default, Maven Install Plugin uses the local repository defined in the settings.xml to install an artifact.

You could install an artifact on a specific local repository by setting the localRepositoryPath parameter when installing.

mvn install:install-file  -Dfile=path-to-your-artifact-jar \
+                          -DgroupId=your.groupId \
+                          -DartifactId=your-artifactId \
+                          -Dversion=version \
+                          -Dpackaging=jar \
+                          -DlocalRepositoryPath=path-to-specific-local-repo
+
+
+
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/specific-local-repo.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/specific-local-repo.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/update-release-info.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/update-release-info.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/update-release-info.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,187 @@ + + + + + Maven Install plugin - Updating the release information of a project + + + + + + + + + + + + + + +
+ +
+
+
+

Updating the release information of a project

Updating the release information means that a forced update of the project's metadata takes place which sets the artifact as the release version. It is most useful when installing a plugin built from source so it can be used by other projects without explicitly asking for the latest SNAPSHOT version.

This can be activated by setting the updateReleaseInfo parameter to true when installing.

  mvn install -DupdateReleaseInfo=true
+
+
+
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/update-release-info.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/examples/update-release-info.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision Added: websites/production/maventest/content/plugins/maven-install-plugin-2.4/faq.html ============================================================================== --- websites/production/maventest/content/plugins/maven-install-plugin-2.4/faq.html (added) +++ websites/production/maventest/content/plugins/maven-install-plugin-2.4/faq.html Mon Sep 3 20:19:45 2012 @@ -0,0 +1,205 @@ + + + + + Maven Install plugin - Frequently Asked Questions + + + + + + + + + + + + +
+ +
+ +
+
+
+ + + \ No newline at end of file Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/faq.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: websites/production/maventest/content/plugins/maven-install-plugin-2.4/faq.html ------------------------------------------------------------------------------ svn:keywords = Author Date Id Revision