[request] Java: to support Gradle: Stop using property variables in POM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Fix Released
|
Medium
|
RaiMan |
Bug Description
Gradle cannot currently resolve SikuliX 1.1.0-SNAPSHOT because of this line "<artifactId>
> Could not find com.sikulix:
Searched in the following locations:
http://
http://
http://
https:/
https:/
https:/
Gradle does not resolve variables in POM files and discourages their use. http://
Sample gradle file:
apply plugin: 'java'
apply plugin: 'idea'
repositories {
mavenCentral()
maven {
url "http://
url "https:/
}
}
dependencies {
testCompile group: 'com.sikulix', name: 'sikulixapi', version: '1.1.0-SNAPSHOT'
}
Version used: 1.1.0-SNAPSHOT
64-Bit Ubuntu 14.04
Java 1.7.0_72 64-Bit
Gradle 2.0
summary: |
- [request] Stop using variables in POM + [request] Java: to support Gradle: Stop using property variables in POM |
Changed in sikuli: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → 2.0.0 |
Changed in sikuli: | |
status: | In Progress → Fix Released |
Interesting - thanks.
I will not fix this for 1.1.0 (the native library package is selected this way based on the system we are running on).
The only workaround currently is to use setup to get a packed sikulixapi.jar for your system and use this in your Gradle setup.
On Linux systems generally one will usually get problems with the stuff from Maven, since in many cases the bundled libVisionProxy.so does not work (wrong or missing dependencies) and has to be built and packed using setup anyway.
So one currently has to live with that.
Version 2 will surely improve the situation, since I plan to switch to Gradle anyway and to reduce the dependencies on native libraries.