[request] Deploy to Maven Central Repository

[lukewpatterson]

Please deploy the Sikuli jars to the Maven Central Repository

Sonatype can help: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

It would make it much easier to consume if I could just enter in the GAV coordinates in my POM instead doing any custom deployments.

[lukewpatterson (lukewpatterson)]

one thing blocking this is the fact that com.melloware:jintellitype:1.3.2 isn't in central

strangely, though, 1.3.1 and 1.3.3 is there, part of fixing this request might be bumping up to 1.3.3

http://www.jarvana.com/jarvana/search?search_type=project&project=jintellitype

[Tsung-Hsiang Chang (vgod)]

We don't use Maven to build Sikuli. Can we still depoly Sikuli jars to Maven Central?
What's the benefits to do this?

[lukewpatterson (lukewpatterson)]

"We don't use Maven to build Sikuli. Can we still depoly Sikuli jars to Maven Central?"

Definitely. Use of Maven, the repository system, implies neither that the project was built with Maven nor does it imply that it is intended to be consumed exclusively by Maven users.

Ant users can deploy to Central and consume from Central. Background:
    * http://maven.apache.org/ant-tasks/index.html
    * http://ant.apache.org/ivy/features.html search for "Out of the box maven repository support"
    * and specifically when using Sonatype's infrastructure: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7c.StageArtifactswithAnt

"What's the benefits to do this?"

* The Maven POM ensures that the dependencies of the project are well defined and documented
    * Even for those that don't care about Maven, this is a benefit

* If Ant-Ivy/Maven consumers want to code to Sikuli, they basically just need to add something like this to their project:
    <dependency>
        <groupId>org.sikuli</groupId>
        <artifactId>sikuli-core</artifactId>
        <version>2.0</version>
        <scope>compile</scope>
    </dependency>
  ... and away they go

* You'll be able to reach many more consumers
    * The cost to entry will be lowered, as it is now every Maven consumer has to do a custom deployment

* The "downloads" page could really just point to Central

There are other benefits I'm not thinking of right now. I'd be happy to investigate specific questions if you have any.

[Sahil (sai-bombay)]

Hi RaiMan,

Please deploy the Sikuliscript.jar to the Maven as i could use this jar file starightway by just adding the dependency tag in pom.xml file instead of adding the jar manually and hen copying it to build path.

Also, it would be helpful in Continous Integration, while resolving the dependencies otherwise the problem will persist.

[renu chudamani (renu-laxman)]

Can we get this sooner than 2015? Can I help in any way?