You know, something just occured to me... if the maven repository starts getting populated with quite a few jars/bundles, wouldn't it be nice to have an OBR sitting on top of it serving up the bundles that have proper manifest data? On a smaller scale, maybe something like this could be built into Archiva?
Just a crazy thought if there are any takers :-D Chris On 1/31/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
Carlos Sanchez wrote: > ok, that's fine, i wanted to get a sense of what would fit in the > bundle plugin as default, what optional, and what won't fit at all ;) Well, if you really want to play with it, I would recommend creating a plugin that does exactly what you suggest and seeing how well it works and if there is general interest. However, if you were just getting a feel for ideas, then you should consider if the default capabilities of the plugin (as described in my other response) meet the needs you are trying to address. I think we all agree that it would be nice if Maven generated JARs could automatically be used as bundles, we just chose different approaches to achieve that. -> richard > > On 1/31/07, Chris Custine <[EMAIL PROTECTED]> wrote: >> 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 >> > >> > >
