How can it NOT generate Import-Package for bundles that are on the
Bundle-Classpath? This means you have unresolved dependencies in your
code, which can give you very nasty problems during deployment and
running the code. That is like putting out class files that have compile
errors.
I think the old plugin is much more suitable than the new plugin for
your strategy.
Kind regards,
Peter Kriens
EE> On 12/5/06, Aaron Siri <[EMAIL PROTECTED]> wrote:
>> Again - like the war-plugin, osgi-plugin (and most other packaging maving
>> plugins that I am familiar with) jar dependencies (with the compile scope)
>> are automatically added to the artifact (in this case, a bundle) as-is and
>> made available to the runtime (in this case added to Bundle-ClassPath.)
EE> I think I've said this a number of times over the course of this
EE> thread, but just to emphasize: +1 on the above. This is exactly the
EE> behavior we need. That and making sure that the plugin is *not
EE> generating Import-Package statements for the stuff that the
EE> Bundle-Classpath jars provide*. (This last thing about Import-Package
EE> is the ONLY thing the old maven-osgi-plugin did wrong.)
EE> Cheers,
EE> -EE
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
