As a follow up...
The plugin auto-generates the Import-Package header entry if the entry
is not specified in the POM file. If the entry is specified in the POM
file, then the plugin will verify its contents.
I just made a modification to the plugin to generate WARNINGs when it
detects a discrepancy, rather than ERRORs as it was previously doing.
The issue here is that the plugin generates an exhaustive list of
everything that needs to be imported by the bundle, including everything
that is referenced by any embedded JAR files. It might be the case that
you don't need to import everything that is referenced internally if you
never use functionality from that part of the code.
-> richard
Enrique Rodriguez wrote:
LECAN Damien wrote:
Hello
I committed this patch.
Great to finally see Peter's contribution in there.
Great news :) It works perfectly until now.
I will fill in new enhancement suggestions.
Do you think this plugin will be hosted by Maven itself later ? Or by
codehaus ?
It would be great if 'osgi-bundle' packaging could be 'official' (as
war, ear, ...)
I agree, osgi-bundle would be an excellent 'official' packaging type
and I believe it would make the configuration slightly easier. With
Peter's contribution and mangen, combined with pulling some of the
bundle manifest headers from elsewhere in the POM, we might be able to
drastically reduce configuration.
Enrique
