PN> - is maven capable of using the resulting bundle as a dependency for
PN> the next bundle (I think not)
The bnd plugin does not use the bundle classpath so the results are
also valid for normal maven dependencies, they are normal jars with
flattened classpaths (unless you hardcode it yourself).
PN> - is the bnd plugin capable to figuring out the imports and exports
PN> from only ingoing .jar files, meaning that more or less all bundles
PN> look like library bundles? (I guess that is there or would be
I think so, but I am not a 100% sure I understand the question ...
Kind regards,
Peter Kriens
PN> Hi Peter,
PN> while reading this i am thinking of one more interesting case.
PN> What about bundles that do not have the source located as class files
PN> under the root of the bundle jar, meaning that the bundle can play a
PN> double role as valid "classic" jar and as a valid bundle?
PN> It is entirely possible, and probably in certain cases, not only
PN> library jars, desirable to package all class files into jars within
PN> bundles. What about maven and the bnd plugin in that case?
PN> - is maven capable of using the resulting bundle as a dependency for
PN> the next bundle (I think not)
PN> - is the bnd plugin capable to figuring out the imports and exports
PN> from only ingoing .jar files, meaning that more or less all bundles
PN> look like library bundles? (I guess that is there or would be
PN> possible)
PN> /peter
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
