有人在巴克明斯特的现实世界中经历过吗？
我目前正在评估 ivy、maven 和 Buckminster，以简化我们的构建过程。 从概念上看，巴克明斯特似乎是最先进的，但也具有相当的复杂性。
我在网上找不到那么多关于巴克明斯特的第一手经验，因此我向 Stackoverflow 社区提出问题。
I'm currently evaluating ivy, maven and buckminster to ease our build process. Conceptually buckminster seems the most advanced, but also to have quite a complexity.
I can't find so many first hand experiences to buckminster on the web, therefore my question to the Stackoverflow community.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们在七月份的构建过程中采用了巴克明斯特。
我们的设置是使用由 CruiseControl 服务器运行的 Ant。
我们选择它是因为我们有多个项目位于多个存储库中。 我们有多种 RCP 产品使用这些项目的不同组合。
总的来说，我发现它是一个非常强大的工具，但文档却很差。 有很多新概念，并且因为它是一个可以插入工具的框架，所以这些概念的一些名称可能非常抽象。
然而，巴克明斯特在解决上述三个问题方面绝对擅长。
其他补充：
缺点（除了缺乏文档之外）：
总的来说，我想说，虽然需要一段时间才能入睡，但做得非常好。 我无法将它与 Ivy 或 Maven 进行比较，尽管 Spring 对 OSGi 的采用可能会在开发人员中对 Maven 产生重要影响。
我已经回答了有关巴克明斯特的几个问题，为您在开始时提供帮助。
We adopted buckminster for our build process in July.
Our set up was to use Ant being run by a CruiseControl server.
We chose it as we have multiple projects living in multiple repositories. We have several RCP products that use different combinations of these projects.
Overall, I found that it is a very powerful tool with poor documentation. There are lots of new concepts, and because it is a framework to plug tools into, some of those names for these concepts can be quite abstract.
However, buckminster absolutely excelled at solving the three problems detailed above.
Other additions:
On the downside (apart from the lack of docs):
Overall, I would say that it took a while to bed in, but does an excellent job. I cannot compare it with Ivy or Maven, though Spring's adoption of OSGi may give critical mass in developer mindshare to Maven.
I have answered a few questions concerning buckminster, for help when you start.
我们使用通过 Jenkins 运行的 Buckminster 来构建一个 KNIME (eclipse) 更新站点，其中包含托管在多个存储库中的多个插件/功能。 最初的决定是因为它是KNIME 社区贡献的构建方式。 有一个学习曲线，但是一旦运行起来。 我们的许多初始设置过程都是基于 开发插件 - 与 Jenkins 持续集成的说明
We use buckminster running via Jenkins to build a KNIME (eclipse) update site with multiple plugins / features hosted in multiple repositories. Initial decision was because that it how the KNIME community contributions are built. There is a learning curve, but once it is running. A lot of our initial setup process was based on the instructions at Developing plugins - continuous integration with Jenkins