Hi Stuart > > the 'bundleall' goal simply takes all your project > dependencies and turns > them into separate bundles > using a very simple "export all" approach - it wasn't > designed to be used to > create Eclipse plugins, > but was more of a 'mass-conversion' tool for simple projects > > > you can configure the maximum dependency depth for > 'bundleall', but you > can't exclude specific items
Ok, so I'll skip 'bundleall' totally. I was trying to avoid having to create a new Maven project, since we're running our Eclipse PDE build as one huge 'blackbox' Maven 'project'. > > the simplest way is to ignore the 'bundleall' goal and change > your POM to > use the 'bundle' packaging, > you'd then get automatic manifest generation, fine control over > embedding/inlining dependencies, and > generation of OBR metadata (handy for when you're deploying bundles) > > look at Embed-Dependency in > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html > to see how to pull dependencies into your plug-in - this will > also let you > filter out unwanted jars Thanks, I know it works because I've done it for individual projects already. Just to be sure: The Felix plugin doesn't download and copy any dependencies, right? Which means I have to use the dependencies plugin to do that. I'm asking because at the moment, I have 40 JAR files downloaded as dependencies (by the dependencies plugin), but even though I specify <Bundle-ClassPath>.,{maven-dependencies}</Bundle-ClassPath> I only have 37 JARs in there. > > you can use the configuration under 'Eclipse/PDE integration' > to generate > the manifest in the place > that PDE expects it and arrange for embedded jars to be where > PDE expects > them (PDE basically > assumes the bundle is unpacked under the project directory, > which conflicts > with the Maven layout) I'm a bit confused about <Embed-Directory> - do I have to specify it for Felix to work correctly? I let the dependencies plugin download all JARs into the project root. > > alternatively look at > http://www.ops4j.org/projects/pax/construct - you can > use these scripts to create > plug-in projects (uses Maven archetypes underneath) and the generated > projects have built-in support > for Eclipse/PDE - just uncomment the "ide-support" execution in the > top-level POM to update the PDE > project information automatically on each build, or use "mvn install > pax:eclipse" (it's like eclipse:eclipse > but has better OSGi support) > > http://www.jroller.com/habuma/entry/pax_construct_from_zero_to Thanks, but I'm getting to know Felix better, and I'm already very glad for what I'm getting here! :-) So, if I can do it with Felix (and Maven's Eclipse plugin), I will. > > also have a look at the Tycho project, which might be a > better fit if you're > primarily working in Eclipse: > > > http://www.sonatype.com/people/2008/11/building-eclipse-plugin s-with-maven-tycho/ > http://docs.codehaus.org/display/M2ECLIPSE/Tycho+user+docs > Thanks, Tycho looks promising for the future, but right now it looks like overkill for what I'm trying to do. Best regards, Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
