On Sun, 07 Mar 2004, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
> With "nobody gives a damn" I meant none of the avalon people.
They are possibly busy bashing each other. Oops, off topic.
> There are two paths here:
>
> 1) make gump smart enough to work with that's out there
The problem w
On Sat, 6 Mar 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
>> I will try to suggest a new build.xml to the avalon team for this
>> component. May be it could be built with Maven, but I do not know
>> Maven, and I do not know either the interface between gump and
>> Maven.
>
> The way is it (w
> But you are right, if the number of dependencies is displayed, it will
> be easier to detect the spots which are harming a lot gump.
I think gumpy suffers from "data overload" syndrome: too many numbers,
too much eye candy... it's harder to spot where the errors are.
One person'
Antoine Lévy-Lambert wrote:
Stefano Mazzocchi wrote:
Dear gumpmaisters,
excalibur-logging is breaking basically 40% of our tree and nobody
gives a damn.
Hi Stefano,
Actually in the last one or two months, I have been "giving a damn" as
you said. With the participation of the corresponding
> Actually in the last one or two months, I have been "giving a damn" as
> you said.
I suspect Stefano meant more from the owners, not all the Gumpmeisters 'cos
we are a caring bunch. ;-) We've noticed all you've achieved ... (hmm, we
need a FOG Factor for a count of projects & dependencies that f
Stefano Mazzocchi wrote:
Dear gumpmaisters,
excalibur-logging is breaking basically 40% of our tree and nobody
gives a damn.
Hi Stefano,
Actually in the last one or two months, I have been "giving a damn" as
you said. With the participation of the corresponding communities,
and the help of
Stefano Mazzocchi wrote:
Dear gumpmaisters,
we need a way to improve the state of our tree.
My idea is simple: send a summary email to this list with the current
state of the tree.
basically a text-based version of
http://lsd.student.utwente.nl/gump/project_todos.html
ranked by some weighing o
> we need a way to improve the state of our tree.
Agreed.
> My idea is simple: send a summary email to this list with the current
> state of the tree.
>
> this should have a list of the build failures, ranked by the number of
> other builds that depend on it.
Not ranked, but isn't this this? The
Dear gumpmaisters,
we need a way to improve the state of our tree.
My idea is simple: send a summary email to this list with the current
state of the tree.
this should have a list of the build failures, ranked by the number of
other builds that depend on it.
For example:
excalibur-logging i
