sikuli-driver team mailing list archive

[RaiMan <question246607@xxxxxxxxxxxxxxxxxxxxx>]

Question #246607 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/246607

RaiMan posted a new comment:
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.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.