« RSS2.0 - have it your way | Main | Small Is The New Big. Or Something. »

Ouch

Steve Loughran: "As a result, every OSS project that depends on JUnit has suddenly stopped building on Gump; That is, 57% of all projects, 441 teams."

Sounds bad. But doesn't that mean lots of apache projects were linking to the JUnit CVS MAIN rather than a label like 3.8.2, or via a versioned maven/ivy binary dependency?

Update from Steve: Gump builds against the head of everything. but:

"What junit did was not only break everything on gump, but provide no warning of it by not updating their public SVN repo. If they had done that, the problem would have been found and worked around a long time ago."

February 18, 2006 04:32 PM

Comments

Dominic Mitchell
(February 18, 2006 06:57 PM #)

I thought that the point of gump was that it always tried to integrate the latest code bases together? See what clashes before the users do.

But I'll admit that I haven't looked closely at it.

Steve Loughran
(February 18, 2006 08:26 PM #)

Gump builds CVS_HEAD/SVN_HEAD of everything; its purpose is to make sure that no changes in unreleased code breaks existing stuff.

You may declare in your maven dependendencies or ant classpath declarations that you want junit3.8.1, but gump ignores it (there are special hooks in ant for that very purpose (see build.sysclasspath))

What junit did was not only break everything on gump, but provide no warning of it by not updating their public SVN repo. If they had done that, the problem would have been found and worked around a long time ago.

It wont stop anybody shipping, but it has broken the nightly build infrastructure

Post a comment

(you may use HTML tags for style)




Remember Me?

Trackback Pings

TrackBack URL for this entry:
http://www.dehora.net/mt/mt-tb.cgi/1753