Open GoogleCodeExporter opened 9 years ago
This seems to have been an issue with our ivy build system integrating with
maven output of javacv. Apparently having two files, one called javacv-0.3.jar
and once called javacv-0.3-macosx-x86_64.jar was causing problems and native
libraries were not being downloaded properly.
Is there any way to instruct the javacv build to produce a single artifact file
with the native libs included?
Original comment by dstiegl...@stainlesscode.com
on 3 Jan 2013 at 12:57
No, because I do not know how something like that should work across
platforms... Do you know of some feature in Maven that I don't know about that
could help with that?
Original comment by samuel.a...@gmail.com
on 3 Jan 2013 at 10:15
BTW, has this issue been fixed with recent versions of Ivy?
If not, we should be reporting that upstream.
Because this naming scheme is pretty standard with Maven.
Thanks for looking into that!
Original comment by samuel.a...@gmail.com
on 29 Apr 2014 at 12:49
Original issue reported on code.google.com by
dstiegl...@stainlesscode.com
on 2 Jan 2013 at 1:00