Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Build Documentation

I should have mentioned that AMP is using Buckminster. I'm almost an anti-case because I've got so many weird dependency issues and I seem to find every difficult case imaginable. But I have worked hard to keep the overall build-time (hudson) configuration as simple as possible and whenever possible to put the logic into a single build system.

I can't speak to tycho, but the principal advantage of Buckminster is that it handles all aspect so of provisioning in an open-ended way but with sensible defaults. The set of artifacts is a bit overwhelming at first so the Buckminster guide is worth a good scan. But once you have a Buckminster build working the really cool thing is that you can use it to provision your development setup as well. So I can now simply grab the Classic Eclipse build, import my project releng directory, open up a cquery file, click Resolve.. and all of my plugins are installed and all of the projects for my build are imported into the workspace.



On Apr 5, 2011, at 1:08 PM, Scott Lewis wrote:

> Hi Mark,
> On 4/5/2011 11:52 AM, Mark Russell wrote:
>> Thanks for the input.  We wrote a custom build system based off of PDE but using Groovy to drive the build.  I want to move to a more "standard" system as I move the code to Eclipse.
>> Which projects are using Buckminster?
> I don't know how many/which other projects are using Buckminster for their builds, but ECF is using combination with the PDE, Athena and other scripts, Maven and Jenkins...and are quite happy with it.'s the server:
> [1]
> Scott
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx

Back to the top