On 17/08/07, Guillaume Sauthier <[EMAIL PROTECTED]> wrote: > > Hi All
Hi Guillaume, First, congratulation to all for the 1.0.0 release and especially to > Rick for his new job in Boston! > > now, my problem :) > I'm just trying to make my first bundle using the felix > maven-bundle-plugin. > As this bundle is intended to have a quite big number of dependencies, > I've created a pom module that only defines all the dependencies. The > this module has been placed in the dependencies section of my bundle's > pom.xml. > looks like this: a --> b --> (c, d, e, f, g, h, i, ...) btw, you can also inherit dependencies from a parent pom First comment, when I just build my bundle, It finish quite soon with a > NPE in JarFile! > -> The bundleplugin only manage jar file as dependencies. It should at > least check the dependency type before assuming this is a jar file. (I > can provide a patch/JIRA if needed) yes, please open a JIRA issue and attach a pom that recreates the bug plus the suggested patch Second one, is this something reasonnable to expect the bundle plugin to > resolve transitively the artifacts dependencies ? I can help too, but > that may have some side effects if we resolve jar dependencies too > (that's a guess, I don't really know...). ideally, we should match with the expected maven behaviour for traversing dependencies at the moment the plugin only uses the dependency list to form the classpath passed onto the BND tool - FELIX-308 will add support for embedding dependencies in the bundle itself What do you think ? > > Thanks > --Guillaume > -- Cheers, Stuart
