Why not add Package-Import for JNA packages to ease JNA-based agent attachment in an OSGi context running with a JRE?

[aleguenn]

Hello,
I am using byte-buddy in an OSGi context, running with a JRE (not a JDK), and therefore wanted to use the JNA-based agent attachment.
The problem is that the byte-buddy-agent bundle has no visibility on JNA by default, even though JNA is also deployed as an OSGi bundle in the same application.
Currently, the MANIFEST.MF file for byte-buddy-agent only contains:
Import-Package: com.sun.tools.attach;resolution:=optional,com.ibm.tools.attach;resolution:=optional
The following change seems to fix the issue for us:
Import-Package: com.sun.tools.attach;resolution:=optional,com.ibm.tools.attach;resolution:=optional,com.sun.jna;resolution:=optional,com.sun.jna.platform;resolution:=optional,com.sun.jna.platform.win32;resolution:=optional,com.sun.jna.win32;resolution:=optional,com.sun.jna.ptr;resolution:=optional
Was such a change ever considered?

[raphw]

This is just an oversight. I added the packages to the master branch. Does this work now? If so, it will be included like this in the next release.

[aleguenn]

Yes, it seems to work just fine here. Thanks for the very quick answer!
Any idea when 1.17.4 will be released? (too bad I reported this too late for the just released 1.17.3).
Regards,

[raphw]

I made a new release. I wanted to activate the safevarargs enhancement anyways, what needed a release to make it available.

[aleguenn]

That's really great!
Do you know how much time it will take for the new release to show up on maven central?

[raphw]

Search indices can take time, but it should be available instantly.

[aleguenn]

Ah yes, you're right, it is already available at https://repo1.maven.org/maven2/net/bytebuddy/byte-buddy-agent/1.17.4/ even though the indices are not updated yet. Thx!