[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [emf-dev] Builds: The never ending nightmare
|
Hi,
I can only agree:
- The first build without redundant releng data
- No extra effort for developer workspace setups
- No new qualifiers for unchanged IUs
- A lot to learn at the beginning, but *excellent* support. Kudos to
Thomas and Achim!
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 25.02.2010 12:13, schrieb Martin Taal:
Hi All,
Teneo is doing builds using Buckminster and it works nicely for me. It
required some setup but I have now good control over the build
process. And the number of configuration files is pretty modest. Also
a multi-step build procedure (build core plugins, create test
environment, run tests) was quite doable.
I liked it that buckminster helps to auto-retrieve dependencies, build
the target platform and setup the build workspace.
The buckminster people have been quite responsive on the newsgroup also.
I don't know the specifics of other builds but I think that both CDO
and Teneo offer good example setups if you want to use buckminster to
do the build.
gr. Martin
Ed Merks wrote:
Guys,
As I mentioned yesterday, CDO has been converted to use Buckminster
with Cloudsmith's help and Teneo is also in the process of doing
that. The Cloudsmith folks are offering to help convert a bunch of
the projects over, starting with the projects in EMF itself, e.g.,
the core. I'd like to see how that progresses. Once all the
subprojects of EMF are successful, we can look at replicating that
success. The advantage of this approach, as I see it, is that we'll
have a dedicated professional build organization to help us with our
common problems going forward. And in the longer term, we'll be able
to easily migrate to b3 as that involves; a model-based build system!
Cheers,
Ed
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev
