I think I understand what you are trying to do as far as getting the
maven-bundle-plugin to use more of the pom.xml data, but I agree with
Richard in saying that Require-Bundle can be troublesome and I definitely
wouldn't want it to be a default mechanism because it would start new users
on the wrong foot if they didn't know any better.
I think in general, there is an impedance mismatch between OSGi bundle
dependencies and Maven project dependencies so for now I am not sure it can
get much better than the what the maven-bundle-plugin does today.
Chris
On 1/31/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
Hi all,
I'm trying to make maven generate OSGi bundles based in the information
of the pom as much as possible. That implies generating "Require-bundle"
headers based on the dependencies section of the pom instead of
autodiscovered "Import-packages".
I'd take groupId.artifactId as bundle name and dependency version as
bundle version.
In the future this could be the standard for any jar generated by Maven.
It will assume that dependencies are already available as OSGi bundles,
although I'm working on a recursive mode that will generate
one bundle for each dependency scanning the whole tree of transitive
dependencies.
Please let me know if this sounds right for the maven-bundle-plugin.
Any comments appreciated ;)
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
