Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for sweet-sop version 1.0

Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for sweet-sop version 1.0. You can add these depency in your project to get com.appslandia:sweet-sop:1.0 Java library in your project.

Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for sweet-sop version 1.0

--Ads--

Maven, Gradle, SBT, Ivy, Grape, Leiningen and Buildr Dependency for sweet-sop version 1.0. You can add these depency in your project to get com.appslandia:sweet-sop:1.0 Java library in your project..

Maven, Gradle, SBT, Ivy, Grape, Leiningen and  Buildr Dependency for sweet-sop version 1.0

In this section have given the dependency code for Maven, Gradle, SBT, Ivy, Grape, Leiningen and  Buildr Dependency for sweet-sop version 1.0. You be able to use the dependency given here for the  sweet-sop version 1.0 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.appslandia

Artifact: sweet-sop

Version: 1.0

In this page we are going to discuss sweet-sop version 1.0 maven dependencies. Maven tool is a project management tool which you use to manage your project and easily use sweet-sop version 1.0 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 sweet-sop version 1.0 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 sweet-sop version 1.0:

<dependency>
	<groupId>com.appslandia</groupId>
	<artifactId>sweet-sop</artifactId>
	<version>1.0</version>
</dependency>

Gradle Dependency of sweet-sop version 1.0

compile group: 'com.appslandia', name: 'sweet-sop', version: '1.0'

SBT Dependency of sweet-sop version 1.0

libraryDependencies += "com.appslandia" % "sweet-sop" % "1.0"

Ivy Dependency of sweet-sop version 1.0

<dependency org="com.appslandia" name="sweet-sop" rev="1.0"/>

Grape Dependency of sweet-sop version 1.0

@Grapes(
    @Grab(group='com.appslandia', module='sweet-sop', version='1.0')
)

Leiningen Dependency of sweet-sop version 1.0

[com.appslandia/sweet-sop "1.0"]

Buildr Dependency of sweet-sop version 1.0

'com.appslandia:sweet-sop:jar:1.0'

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