Hi Jochen, You may want to look at Sigil [1] which is hosted here at Felix. This uses exactly the approach you suggest in that it resolves package dependencies from OSGi manifest files.
To see an example of a sigil build in action you may want to check out a recent blog post [2] I made which is actually related to our product but uses a sigil build to create the necessary bundles. Very happy to receive feedback, issues or code contributions in this area :) Regards, Dave [1] http://felix.apache.org/site/apache-felix-sigil.html [2] http://chronological-thought.blogspot.com/2009/11/hello-tatooine.html On Thu, Dec 3, 2009 at 1:24 PM, Jochen Mader <[email protected]> wrote: > Quite simply: I don't like my build process. > I am looking for a way of doing builds that stays true with the OSGi > philosophy. > I got my builds going with Maven, BND and OBR. But looking at the poms > always gives me the shivers. > The thing that drives me nuts is the replication of dependency information > (the maven shotgun approach of "give me the bundle" vs the OSGi sniper > approach "give that package"). > We have to specify the dependencies once to do our build and a second time > to generate the manifest (BND). > I can't make use of the extended meta information an OSGi bundle contains > to, let's get wild, resolve my dependencies AND transitive dependencies from > an OBR. > Is there some work being done that goes into that direction? Probably a > project I could join? > Something like maven plugin that replaces the dependency declarations with a > "go to BND and grab the information from there as we are way too lazy to > type that stuff more than once" :) > > CU > > Jochen > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
