(-main deploy-or-install artifact & [sign-releases])(all-artifacts sign? {:keys [version] :as coordinates} artifact)(artifacts version files)(classifier version f)The classifier is be located between the version and extension name of the artifact. See http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
The classifier is be located between the version and extension name of the artifact. See http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
(coordinates-from-pom pom-str)(deploy {:keys [pom-file sign-releases? artifact] :as opts})The main entry point into deps-deploy via tools.deps :exec-fn which supports an opts map that can be supplied via :exec-args.
Required keys are:
:artifact A string specifying the file path relative to the current working directory to the artifact to be deployed. This will normally be your library packaged as a jar.
:installer Set to either :local or :remote depending on whether you want to install into your local .m2 cache or to a remote :repository.
:pom-file defaults to "pom.xml"
:sign-releases? A boolean that specifies whether releases should be signed
The main entry point into deps-deploy via tools.deps :exec-fn which
supports an opts map that can be supplied via :exec-args.
Required keys are:
:artifact A string specifying the file path relative to the current
working directory to the artifact to be deployed. This will
normally be your library packaged as a jar.
:installer Set to either :local or :remote depending on whether you
want to install into your local .m2 cache or to a remote
:repository.
:pom-file defaults to "pom.xml"
:sign-releases? A boolean that specifies whether releases should be
signed
(mvn-coordinates {:keys [group-id artifact-id version]})(sign! pom jar-file)cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |