Just a point did you test the last versions 3.4.0 or 3.4.1. If you look more closely you will see an exception on the header parsing or Pax automatically wrap it in a bundle as it is not a valid osgi manifest. After a quick review of the manifest it is simply a blank line and a ',' at the end of the Native block. In the current trunk of the JNA repository the fix is already in place we just have to wait for the next release.
Romain Le mardi 4 septembre 2012, Romain Gilles a écrit : > Thank you guys for this information. > > Romain > > Le vendredi 31 août 2012, Jean-Baptiste Onofré a écrit : > >> JNA (for Java Native Access) is an alternative of JNI (Java Native >> Interface). It allows to load and use native libs (dll for windows, so for >> Unix dynamic, etc). JNA is easier to use than JNI and provide a kind of >> proxy (avoiding to write a Java/C wrapper for instance). >> >> Jline console leverages native lib (especially on Windows) for coloring, >> etc. It uses JNA for that. >> >> Regards >> JB >> >> On 08/31/2012 03:55 PM, Achim Nierbeck wrote: >> >>> Hi, >>> >>> IIRC this has been included into jline also for windows somewhere >>> between 2.2.0 and 2.2.5. >>> so it's not needed anymore. >>> >>> regards, Achim >>> >>> 2012/8/31 Romain Gilles <[email protected]>: >>> >>>> Hi all, >>>> I would like to know what it introduced by the jna lib? Currently when >>>> I'm >>>> using karaf it is already colorized without executing the following >>>> documentation step: >>>> http://karaf.apache.org/**manual/latest-2.2.x/users-** >>>> guide/colorized-console.html<http://karaf.apache.org/manual/latest-2.2.x/users-guide/colorized-console.html> >>>> >>>> Romain >>>> >>> >>> >>> >>> >> -- >> Jean-Baptiste Onofré >> [email protected] >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> >
