One of the things I look for when I'm evaluating a java library, is whether or not maven artifacts are available. I noticed that OpenCV makes you download and compile the source code. WHy is that?
We have an open ticket about this feature: http://code.opencv.org/issues/3097
I have a sample project that shows how to use OpenCV through Maven: https://github.com/JavaOpenCVBook/code/tree/master/chapter1/maven-sample (Notice: it requires adding a custom repository, so I would really like to see OpenCV supporting it instead of having to add another repository)
My idea is really to put this in the build process of OpenCV. Binaries should be generated with their version control. Could you please add another request for it in the issue thread ( http://code.opencv.org/issues/3097). Maybe if enough people comment, there could be more attention from OpenCV people.
hi Daniel,
PR == pull request
unfortunately, i got not much information about the build/deploy process for binaries, (think of the (win) sourceforge packages or the prebuild android sdk), but taking a look at the buildbot used for testing might be a start.
if you look at the comments on the issues page, the common answer is: yes, good idea, but it's up to you to act now, and develop that.
Asked: 2014-03-31 13:48:19 -0600
Seen: 12,825 times
Last updated: Oct 20 '14
you're probably the 1st one to come up with that idea here
bear with me for not knowing much about maven, but again, opencv-XXX.jar is only half of the story.
you'd need the opencv dll/so's compiled for any platform you can think of as well.
what's your idea on that ? also, dependancies ? ffmpeg, the like ?
continous integration from github src ?
@berak I don't know about ant, but in maven there is a way to add native library dependencies http://mojo.codehaus.org/maven-native/native-maven-plugin/usage.html
honestly, you probably know more about java package managing than i do.