~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~~ KIND, either express or implied. See the License for the
~~ specific language governing permissions and limitations
-~~ under the License.
+~~ under the License.
+
+~~ NOTE: For help with the syntax of this file, see:
+~~ http://maven.apache.org/guides/mini/guide-apt-format.html
Deploying to Repository
There are different ways on how you can deploy artifacts in an Archiva repository.
- * {{{#Maven} Configuring Maven to deploy to an Archiva repository}}
+ * {{Maven}} Configuring Maven to deploy to an Archiva repository}}
- * {{{#Web UI} Deploying via the Web UI Form}}
+ * {{Web UI}} Deploying via the Web UI Form}}
Starting with Archiva 1.2.3, it is possible to block re-deployment of released artifacts to a specific repository. This can be configured through the
repository configuration page by ticking the <<<Block Re-deployment of Released Artifacts>>> checkbox.
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
- <artifactId>wagon-webdav</artifactId>
- <version>1.0-beta-2</version>
+ <artifactId>wagon-webdav-jackrabbit</artifactId>
+ <version>2.2</version>
</extension>
</extensions>
</build>
Alternately, you can save this file somewhere else, and use "<<<mvn ... -f
/path/to/filename>>>" to force the use of an alternate POM file.
-
+
* Deploying via the {Web UI} Form
The easiest way to deploy in the repository is via the Web UI form, which can be accessed in the <<Upload Artifact>> section.
* Packaging - the packaging of the artifact to be deployed. (ex. jar, war, ear, etc.)
- * Artifact File - the actual artifact to be deployed.
+ * Drag and drop files to be deployed.
[]
[[4]] Now, if you want Archiva to generate a pom for the artifact, check the Generate Maven 2 POM field.
(Right now, only Maven 2 poms can be generated.) Alternately, supply a POM file to be deployed alongside the artifact.
- [[5]] Click Submit and a message will be displayed notifying you if the upload/deployment was successful or not.
+ [[5]] Click Saves files and a message will be displayed notifying you if the upload/deployment was successful or not.
[]
[../images/upload-artifact.jpg] Upload Artifact
- <Note:> The maximum size of the file that can be uploaded is 10M by default. To alter the setting, change <<<struts.multipart.maxSize>>> in the file
- <<<WEB-INF/classes/struts.properties>>> in the Archiva web application (located under <<<apps/archiva>>> in the standalone distribution).
-
- The upload form also provides validation checks against the required fields and the version. In Archiva 1.2.1, the version checking has been
- loosened. See {{{http://jira.codehaus.org/browse/MRM-1172}MRM-1172}} for more details.
-
~~TODO: information for Maven 1, ant tasks, ivy, etc.