From what I understand (and that is usually pretty limited), b3 is a build technology (same category of technologies as Maven, Ant, PDE/Build, etc...). The problem here (also faced by many Eclipse projects) is not the choice of build technology, but rather build infrastructure. How are the builds being run, how are they propagated, how are errors reported, who handles the errors, who gives the +1 / -1 to the builds, etc...
I think (again, I could be wrong) this is where Athena enters the picture. From a technology adoption standpoint, using b3 may make perfect sense, but I'm not sure it solves the problem that Dave and Marcelo raised.
Maybe b3 is aimed to bring the build technology and build infrastructure gap closer together, and if so great! Maybe someone with more knowledge of the b3 project could comment here.
I was just signifying the fact that you spoiled the plot of a "good
science fiction movie" which some people might want to watch too. I
tried to keep the constructive tone you used in your note.
Going back to the EMF issue : obviously some people cares about the
build (I do !) and moving it to Athena would ease the integration of
new people to maintain it.
Le 25/01/2010 11:15, Vlad Varnica a écrit :
We are not at my children's garden Junior School so please explain your
point of view and don't reply such a way.
Cédric Brun wrote:
Le 25/01/2010 10:58, Vlad Varnica a écrit :
I watched a good science fiction movie named "The day the earth Stood
Still" last week on my SkyBox last week.
Keen Reeve was an Alien named Klaatu" coming to earth to decide how to
save the earth.
He had long talks etc....but at the end his conclusion was that the
only way to save the earth was to get rid of human being and let
animals leave in peace.
Hopefully a professor explained to the Alien that: "all
civilizations only change when they're at the precipice of a crisis.
He says human will change, now that they are really at the edge of
At the end of the movie the sphere and Klaatu have disappeared. Then
EVERYTHING shuts down -
lights, buildings, cars, etc. People everywhere cautiously emerge.
Do you think there is a parallel between EMF and the edge of
Dave and I have been talking
builds and the issue worry us a bit. Although most of the work can be
the build does require some attention: from running scripts and
test results on a regular basis, to actually maintaining the build in
to provide new artifacts or fix something that got broken due to
in a dependency. Since neither Dave nor I can assume this
ideally someone else would step up to task. This person would hopefully
be committed to all parts of code and, for example, make some noise
if a test focused on a less important piece fails (a test for the
support for example).
An alternative to have a
working on this is to gather a pool of people and share the burden.
and I could be members of this pool, if this makes sense.
Btw, if it helps making this
little more exciting, Dave and I are willing to move the EMF build to
(Nick has already done some of the required work!). Obviously "old
build or Athena" is a completely irrelevant matter if no one cares
about EMF builds. If that's indeed the case, is it OK if EMF doesn't
a new build? All affected projects, people, and companies are OK with
Anyhow, the microphone is open
Any input is welcome.
I'm going to be changing jobs at IBM in a week, and as result, working
on EMF will not be part of my "day job." I'd like to remain a
committer and stay involved in the project as much as possible.
One responsibility that I'll need to shed, however, is the EMF Core
Mostly this has just meant pushing buttons on the build system that
built, ensuring things work, and manually filling in the gaps when they
don't. But I don't feel I can be the single point of failure for
EMF built and promoted anymore.
So I'm wondering if someone else is willing to take primary
for build stuff, or if we could somehow share it amongst committers?
would it be helpful to finally move to the Athena Common Build, or to
enhance the existing modeling build? It would be great if we could have
builds automatically run when new changes are committed and have weekly
I builds promoted automatically if they are clean (no build or test
If there's some work that's needed up-front to make things easier in
future, I'm willing and able to contribute some effort now. Marcelo has
indicated to me that he's willing to help, too.