Closed GoogleCodeExporter closed 8 years ago
Hi fullung,
Thanks for your report :)
I indeed wish I knew how to better use the maven shade plugin... Hopefully a
well-
located exclusion of the .sf files will help, but in the meanwhile you have two
workarounds :
- run the .jar with -noverify
- build the whole nativelibs4java tree following these build instructions
closely :
http://code.google.com/p/javacl/wiki/Build.
Your issue comes from the fact that you're building jnaerator without signing,
but
doing so you're implicitely downloading dependencies from NL4J's FTP that are
signed
(hence a mismatch, as I forgot / failed to exclude the dependencies' signature
files
from the shaded Jar ; java then believes the signature is for the whole shaded
jar,
while it only covers a small part of it). If you build and install all these
dependencies in your local Maven repository, everything should be consistent.
Cheers
Original comment by olivier.chafik@gmail.com
on 7 Apr 2010 at 9:31
Hi,
This issue moved to Github :
https://github.com/ochafik/nativelibs4java/issues/140
Thanks for not updating this page anymore and adding further comments on Github.
Cheers
--
zOlive
Original comment by olivier.chafik@gmail.com
on 1 Sep 2011 at 7:25
Original issue reported on code.google.com by
fullung@gmail.com
on 7 Apr 2010 at 7:07