Closed GoogleCodeExporter closed 8 years ago
Hi
We put these in pom.xml of sikuli-core, which sikuli-api depends on:
<repositories>
<repository>
<id>JavaCV Maven</id>
<url>http://maven2.javacv.googlecode.com/git/</url>
</repository>
<repository>
<id>JavaCPP Maven</id>
<url>http://maven2.javacpp.googlecode.com/git/</url>
</repository>
</repositories>
See:
http://search.maven.org/remotecontent?filepath=org/sikuli/sikuli-core/1.0.0/siku
li-core-1.0.0.pom
Did these statements work at all for you?
We would appreciate if you can provide us with more information about the
trouble you ran into so we can better instruct users how to handle JavaCV and
JavaCPP.
Thanks!
Tom
Original comment by doubles...@gmail.com
on 28 Oct 2012 at 2:03
Ah interesting.
I use Gradle instead of Maven, but it supports Maven repositories. Perhaps its
support lacks in pulling in repos transitively?
I don't know much about Maven and haven't tried a Maven-only scenario.
Original comment by jasonpar...@gmail.com
on 28 Oct 2012 at 2:11
Your right, adding url "http://maven2.javacpp.googlecode.com/git/" to the
Gradle dependencies does fix the JavaCPP error but does not fix the 2nd error
concerneing JavaCV. Will need to track down the repo where JavaCV is also
located.
Original comment by django...@gmail.com
on 3 Nov 2012 at 9:58
In my build.gradle file on Spring Suite 32-bit (the Grails version) I got it
working with these build.gradle dependencies:
repositories {
mavenCentral()
maven {
url "http://maven2.javacpp.googlecode.com/git/"
}
maven {
url "http://maven2.javacv.googlecode.com/git/"
}
}
dependencies {
// stored at: %HOMEPATH%\.gradle\caches\artifacts-14\filestore
testCompile group: 'org.sikuli', name: 'sikuli-api', version: '1.0.0'
compile group: 'commons-collections', name: 'commons-collections', version: '3.2'
testCompile group: 'junit', name: 'junit', version: '4.+'
testCompile group: 'org.seleniumhq.selenium', name: 'selenium-java', version: '2.+'
}
Original comment by django...@gmail.com
on 3 Nov 2012 at 10:02
Original comment by doubles...@gmail.com
on 7 Dec 2012 at 8:21
Original issue reported on code.google.com by
jasonpar...@gmail.com
on 25 Oct 2012 at 3:42