Artifactory offers configuration-based deployments in two forms:
Deploying a Single Artifact
Single-artifact deployment is performed from the Deploy tab and then
Deployment is a two-step process:
Maven vs. Non-Maven Deployment
You can choose between Maven and non-Maven artifact deployment.
When deploying a Maven artifact you can edit the auto-filled GroupId, ArtifactId, Version, Classifier and Type details. The changes you make are auto-reflected in the target path displayed. You can ask for automatic POM generation if one is missing in the target repository and you can even edit the POM manually (make sure you know what you are doing!).
For non-Maven artifacts, such as Ivy artifacts that do not have to follow the Maven repository layout convention, you can deactivate the
Once you are happy with the deployment details, mark the
Deploying a Bundle of Artifacts
Bundle deployment is performed from the Deploy tab and then Deploy ->
This is a very convenient feature for deploying multiple artifacts in one go. The following archive extensions are supported: zip,tar,tar.gz,tgz
Artifacts should be packaged in an archive and contained in the file structure they should be deployed with. For example, the structure of the (partial) archive for Hibernate appears as follows:
Uploading and deploying the archives is a single step ending with all archived artifacts deployed into the selected repository.