The OSGi plugin has several flaws

I’ve tried the plugin posted by Simon, and while I truly appreciate the effort, my conclusion on using it for a few days is that it will require far too many changes to our build because of its use of bnd for creating the jar. The example I posted 3 days ago is just one of the cases. There are numerous others where it’s a force-fit to transform jar closures into bnd instructions and get what we need. In some cases I couldn’t get the jar contents to be complete.

I have around 90 modules that I need to generate, so its a significant effort to get this right using our existing gradle build (of 500+ modules).

I’d like to see the gradle folks work with Peter as they tried to do some months ago to improve upon, or replace the gradle osgi plugin so that this can be accomplished in a style that is more in concert with the existing jar task but does not circumvent the bnd tool analysis.

If Simon’s tool could do that instead, that’s fine too :slight_smile:

Thanks all.

Jim