|How to include binary bundles from "pluginPath" in feature output? [message #590195]
||Thu, 22 January 2009 21:05
| Mark Melvin
Registered: July 2009
I have a continuous integration server building all of my plugins
separately, and I am now using those plugins to build the features. I
supply all dependencies in binary form and point to them using the
"pluginPath" attribute of the eclipse.buildScript Ant target. This all
works great and my feature is built with all of the appropriate version
numbers substituted. However, I can see of no way to easily package up
the features and plugins that were dependencies of the feature I just
built. I am trying to make an update site zip of all features and plugins
included in the feature I am building and it looks impossible without
ripping apart the feature.xml myself to find everything (and doing this
recursively to find dependencies of nested features).
Am I missing something here? Is there a magical flag I can pass
eclipse.buildScript that will include all children - even if they were
pre-build binaries on the pluginPath?
While I'm on the topic - what the heck is "filteredDependencyCheck"
supposed to achieve? I have tried setting this property both ways and it
appears to do nothing in my situation. The docs mention that it is
"optional, constraint the set of plug-ins and features to be considered
during the build to those reachable from the features" - but I still have
yet to figure out what that means.
Powered by FUDForum
. Page generated in 0.01534 seconds