sikuli in Maven Central

Asked by Claes Harvenberg

I can see from previous answers that there are plans to upload sikuli to Maven Central. Would you have a better idea of when that will happen?

Question information

Language:
English Edit question
Status:
Solved
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Solved by:
RaiMan
Solved:
Last query:
Last reply:
Revision history for this message
Best RaiMan (raimund-hocke) said :
#1

Based on my current plans and possibilities it will surely be later than July/August this year and it will only be for version 1.1.0+

Revision history for this message
Claes Harvenberg (claes-harvenberg) said :
#2

Thanks. That answers my question. It is a bit disappointing as not having it in Maven Central causes extra work for us when we want to use Sikuli.

Revision history for this message
RaiMan (raimund-hocke) said :
#3

Yes, I understand your answer, but I have to set priorities.

This is what I currently have and what I plan or have to solve:

- an account on Sonatype JIRA
as far as I understood, one uploads via Maven the artefacts and then they are synchronised to Maven Central after a JIRA request

- principally I am prepared to sign the jar(s) using PGP (I have registered a public key) (I understood, that only signed jars are accepted)

- I want to publish with the group-id com.sikulix (org.sikuli is blocked by Tom Yeh (one of the former developers) with the Sikuli Java API package)

- the artefact people need in Maven projects beginning with version 1.1.0-BetaX is sikulixapi.jar (sikuli-java.jar before with 1.1.0)

*** problems (challenges ;-) I am facing:

- the jar still contains native libraries as binary stuff including dependent libraries for Windows, Mac and Ubuntu 12.xx+
… how to deal with sources (the API at the native level is completely internal).

- must there be one artefact for each system (Windows, Mac, Ubuntu 12+, Linux (not Ubuntu 12+) or is one artefact for all systems ok (which then would contain the lib-sets for all systems and be a some MB bigger)?

- sikulixapi.jar is fully self contained and does not need any other dependencies - so how exactly should the poms and jars (docs and sources) have to look like?

this is my status.
The status of development is here: https://github.com/RaiMan/SikuliX-2014.
Currently I am struggling to create and document reliable workflows to create the library sets (Mac and Windows ok, next is Ubuntu).

If anyone can guide/help me to make the next steps, I surely will be able to step into Maven Central somewhat earlier.

Revision history for this message
Claes Harvenberg (claes-harvenberg) said :
#4

Thanks RaiMan, I understand. I haven't uploaded anything myself to Maven Central and it would be no good me guessing about mechanism or policy. You'd think someone responsible for Maven Central would be happy to answer those questions as they seem pretty straight-forward and there must be a lot of well established patterns that cover your question marks.

Revision history for this message
RaiMan (raimund-hocke) said :
#5

@ Claes
Ok, thanks.

No problem, I only took the chance to document my current status on that.
May be someone stumbles upon this entry and already has a hint on "a well established pattern" useable in this case.