Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for charm-down-plugin-lifecycle version 3.8.1

Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for charm-down-plugin-lifecycle version 3.8.1. You can add these depency in your project to get com.gluonhq:charm-down-plugin-lifecycle:3.8.1 Java library in your project.

Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for charm-down-plugin-lifecycle version 3.8.1

Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for charm-down-plugin-lifecycle version 3.8.1. You can add these depency in your project to get com.gluonhq:charm-down-plugin-lifecycle:3.8.1 Java library in your project..

Maven, Gradle, SBT, Ivy, Grape, Leiningen and  Buildr Dependency for charm-down-plugin-lifecycle version 3.8.1

In this section have given the dependency code for Maven, Gradle, SBT, Ivy, Grape, Leiningen and  Buildr Dependency for charm-down-plugin-lifecycle version 3.8.1. You be able to use the dependency given here for the  charm-down-plugin-lifecycle version 3.8.1 just by copying and pasting your project. One you build your project the respective build tools Maven, Gradle, SBT, Ivy, Grape, Leiningen and  Buildr Dependency will download the jar file and include in your project.

Maven Artifact details:

Group: com.gluonhq

Artifact: charm-down-plugin-lifecycle

Version: 3.8.1

In this page we are going to discuss charm-down-plugin-lifecycle version 3.8.1 maven dependencies. Maven tool is a project management tool which you use to manage your project and easily use charm-down-plugin-lifecycle version 3.8.1 dependency by just including the code discussed here in the pom.xml file of your Maven project.

Maven dependency automatically downloads the dependent library of charm-down-plugin-lifecycle version 3.8.1 and includes the necessary jar files in the project.

Code given here should be included inside <dependencies> ...... </dependencies> tag in the Maven configuration file pom.xml.

We also explained to you the dependency code of different build systems like Gradle Dependency, SBT Dependency, Ivy Dependency, Grape Dependency etc.

Maven dependency of charm-down-plugin-lifecycle version 3.8.1:

<dependency>
	<groupId>com.gluonhq</groupId>
	<artifactId>charm-down-plugin-lifecycle</artifactId>
	<version>3.8.1</version>
</dependency>

Gradle Dependency of charm-down-plugin-lifecycle version 3.8.1

compile group: 'com.gluonhq', name: 'charm-down-plugin-lifecycle', version: '3.8.1'

SBT Dependency of charm-down-plugin-lifecycle version 3.8.1

libraryDependencies += "com.gluonhq" % "charm-down-plugin-lifecycle" % "3.8.1"

Ivy Dependency of charm-down-plugin-lifecycle version 3.8.1

<dependency org="com.gluonhq" name="charm-down-plugin-lifecycle" rev="3.8.1"/>

Grape Dependency of charm-down-plugin-lifecycle version 3.8.1

@Grapes(
    @Grab(group='com.gluonhq', module='charm-down-plugin-lifecycle', version='3.8.1')
)

Leiningen Dependency of charm-down-plugin-lifecycle version 3.8.1

[com.gluonhq/charm-down-plugin-lifecycle "3.8.1"]

Buildr Dependency of charm-down-plugin-lifecycle version 3.8.1

'com.gluonhq:charm-down-plugin-lifecycle:jar:3.8.1'

The remote public repository is very useful and it allows the developers to download Java library jar files very conveniently just by adding the respective dependency code in their project's build tools configuration.

Relevant Tutorials