OSGi Manifest Headers about jna HOT 7 CLOSED

@whatnick: you seem to know what to do here, why not fork the project and make a pull request?

from jna.

fork and push, my friend!

On Jul 6, 2011, at 7:52 PM, whatnick wrote:

Copy of JNA-138:

Would you please be so kind to update the MANIFEST.MF file with OSGi bundle
headers so we could use it in an OSGi environment without repacking the lib?

Something like this (comming from the SVNKit):

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 1.4.2_17-b06 (Sun Microsystems Inc.)
Bundle-ManifestVersion: 2
Bundle-Name: JNA Library Plug-in
Bundle-SymbolicName: com.sun.jna
Bundle-Version: 3.1.0
Bundle-RequiredExecutionEnvironment: J2SE-1.4
Bundle-ClassPath: jna.jar
Export-Package: com.sun.jna,com.sun.jna.win32,com.sun.jna.ptr
Bundle-Vendor: Timothy Wall
Bundle-ActivationPolicy: lazy

This can be done easily using the existing build system and the bnd plugin in Maven or Ant at the jar/package stage.
http://www.aqute.biz/Bnd/Ant

Reply to this email directly or view it on GitHub:
#7

from jna.

I double checked the build.xml and the jar target includes what I need ,(i.e. Manifest entries) handcoded instead of injected by bnd. That is not a blocker. However, the jna.jar and platform.jar available for download seem to come from a separate target and do not have these manifest entries. The platform specific jars will need a Bundle-Native entry - http://robertvarttinen.blogspot.com/2008/12/bundle-nativecode-in-osgi-manifest.html . I have started a fork and will cover Win32, OS-X and Linux 64, these being the VM's I am running mostly on. If you could clarify why the release jar is different from the one built by the ant jar target it would be great.

from jna.

On Jul 7, 2011, at 9:31 PM, whatnick wrote:

I double checked the build.xml and the jar target includes what I need ,(i.e. Manifest entries) handcoded instead of injected by bnd. That is not a blocker. However, the jna.jar and platform.jar available for download seem to come from a separate target and do not have these manifest entries. The platform specific jars will need a Bundle-Native entry - http://robertvarttinen.blogspot.com/2008/12/bundle-nativecode-in-osgi-manifest.html . I have started a fork and will cover Win32, OS-X and Linux 64, these being the VM's I am running mostly on. If you could clarify why the release jar is different from the one built by the ant jar target it would be great.

Reply to this email directly or view it on GitHub:
#7 (comment)

I don't know why they would be different; i'll take a look when I get a chance. I typically do an "ant dist" on the different native targets and build a final jna.jar when all the native jars are collected in one place.

from jna.

I checked on the jna.jar build; turns out the manifest stuff is in the wrong location and gets overwritten when the jars are aggregated for distribution.
I'll fix that.

On Jul 8, 2011, at 7:11 AM, Timothy Wall wrote:

On Jul 7, 2011, at 9:31 PM, whatnick wrote:

I double checked the build.xml and the jar target includes what I need ,(i.e. Manifest entries) handcoded instead of injected by bnd. That is not a blocker. However, the jna.jar and platform.jar available for download seem to come from a separate target and do not have these manifest entries. The platform specific jars will need a Bundle-Native entry - http://robertvarttinen.blogspot.com/2008/12/bundle-nativecode-in-osgi-manifest.html . I have started a fork and will cover Win32, OS-X and Linux 64, these being the VM's I am running mostly on. If you could clarify why the release jar is different from the one built by the ant jar target it would be great.

Reply to this email directly or view it on GitHub:
#7 (comment)

I don't know why they would be different; i'll take a look when I get a chance. I typically do an "ant dist" on the different native targets and build a final jna.jar when all the native jars are collected in one place.

from jna.

I have made bnd based manifests and commented out the old style (handcoded manifests), if you can apply my pull request then make some changes it will be great.

from jna.

Pull request sent see #8

from jna.