Eclipse 功能的无头构建 - PDE 工具还是 Buckminster？
我正在尝试为大型 Eclipse 功能设置无头构建，其中包含其他功能和插件。
由于一些所需的插件是使用 GMF 和 EMF 生成的，因此构建工作流程必须如下所示：
- SVN Check-out
- Invoke Generation
- Run Tests
- Build all
- Publish update-site
在过去的几周里，我使用了 PDE Headless Build 和 Buckminster 。 无论如何，我仍然对两者都有问题，无法决定我应该花精力在哪一个上。
那么你更喜欢什么？ 你有什么经历？ 有人以前需要设置类似的工作流程吗？
谢谢您的所有回答:)
I am trying to set up a headless build for a big eclipse feature, containing other features and plugins.
As some needed plugins are generated using GMF and EMF, the build workflow must be something like this:
- SVN Check-out
- Invoke Generation
- Run Tests
- Build all
- Publish update-site
Over the last couple of weeks, i played around with PDE Headless Build and Buckminster. Anyhow i still got problems with both and can't decide on which i should spent my effort.
So what would you prefer? What experience you made? Anybody out there who needed to set up a similiar workflow before?
Thank you for all answers :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
Buckminster 位于 PDE 构建之上，因此在不久的将来无法摆脱 PDE 构建。
您可以尝试另一个位于 PDE 构建之上的免费插件：Plugin Builder 因为它会生成ANT XML 和 PDE 构建所需的讨厌的映射文件。 它甚至具有基于 SVN 的地图文件（而不是 CSV）的扩展名。 我成功设置了从 Hudson 运行的 Plugin Builder，以满足我团队的构建需求。
另一种选择是查看 Tycho （Tycho 是 OSGi/Eclipse Maven 下一版本的相关部分）。 它是一个正在进行的工作，并且它确实在幕后使用 PDE 构建。 我尝试使用第谷进行一些实验，但失败了，但他们最近确实有一个新的 alpha/beta 版本，因此您可能会取得更大的成功（并且还有其他人正在成功使用它）。
Buckminster sits on top of PDE build, so there's no getting away from PDE build in the near future.
You could try another free plug-in that sits on top of PDE build: Plugin Builder as it does the generation of the ANT XML and the nasty map file that PDE build requires. It even has the extension for SVN-based map files as opposed to CSV. I successfully setup Plugin Builder running from Hudson for my team's build needs.
Another alternative is to look at Tycho (Tycho is the OSGi/Eclipse related bit of the next version of Maven). It is a work-in-progress and it does use PDE build under the covers. I tried and failed with some experiments with Tycho, but they do have a recent new alpha/beta build, so you may have more success (and there are other people who are successfully using it).
我在 PDE 构建中遇到的唯一问题是用于签出的地图文件。 我编写了自己的 ant 任务，根据插件所在位置的约定，使用 SVN 为我进行结帐，而不必在映射文件中显式说明所有文件路径。 创造了奇迹，现在我只需将插件添加到我的 svn 存储库并在 feature.xml 中引用它们，它就可以工作了。
The only problem I've had with PDE build is the map file for checking out. I wrote my own ant task to do the checkout for me using SVN, based on conventions on where the plugins are located, instead of having to explicitly state in the map file all the file paths. Worked wonders and now I can just add plugins to my svn repository and refer to them in the feature.xml and it just works.
我们正在使用 Buckminster 进行构建（检查、编译、测试和字节混淆）。 我还没有尝试过 PDE 脚本，但如果您有一个复杂的设置，并且对其他库/项目有很多依赖性，我认为巴克敏斯特会更好地扩展。
We're building using buckminster(check out, compiling, testing and byte obfuscation). I haven't tried a PDE-script, but if you have a complicated setup with a lot of dependencies on other libraries/projects I think buckminster will scale better.
我最近开始将整个 Eclipse 构建基础架构从 PDE 构建迁移到 Buckminster，并且我对 Buckminster 的评价大多是好的。 虽然基于 PDE 构建脚本/模板的构建往往非常脆弱，并且需要大量的周围基础设施才能工作，但 Buckminster 感觉非常强大，并且不需要任何重要的额外脚本。 Buckminster 确实需要一段时间才能进入，但由于出色的文档和非常有用的新闻组，我能够在几天内获得完整的构建。
Buckminster 是 Eclipse 从一开始就应该拥有的来处理无头构建的工具。
I've recently started to move our entire Eclipse build-infrastructure from PDE build to Buckminster, and I have mostly good things to say about Buckminster. While builds based on the PDE build scripts/templates tend to be very brittle and requires a large amount of surrounding infrastructure to work, Buckminster feels quite robust and does not require any significant additional scripting around it. Buckminster does take a while to get into, but thanks to the excellent documentation and the very helpful newsgroup, I was able to get a full build to work in a few days.
Buckminster is what Eclipse should've had from the very beginning to handle headless builds.