| [news.eclipse.tools.buckminster] Re: Best way to include launchers in an RCP build |
Hi Tas,
stuff deleted...>
Not sure what you're saying here. Are you trying to build a product without including the plug-in that defines the application, and that fails with Buckminster but works with PDE-build?If I add the application plug-in to the configuration tab of the product configuration the product works. What's happening here? Is PDE adding some configuration by default?
Can you please file a bugzilla for this? The equinox executable feature is not intended for runtimes. It's to be considered a pure build-time feature and the inclusion of it should be necessary.Also, looking at the issue of having to include the executables feature, it has another unpleasant side effect of making the feature available in the resulting p2 repository which I don't want.
I agree that this can be improved and as I said earlier, we're working on it. Please set the priority on the bugzilla to major and stay tuned :-)I really want to have a buckminster build which can produce similar results from the same source currently processed by a PDE build. I think many people migrating from PDE Build to buckminster will want this.
To workaround these issues I am having to consider using buckminster only for materializing the target platform and fetching the source and then handing things over to PDE Build for to create the p2 repository. However I would lose the revision based qualifier substitution which I find very useful. Any suggestions as to how I can work around would be greatly appreciate. Maybe it's easier to help resolve these problem in buckminster?
Regards, Thomas Hallgren