At 11/15/2002 02:33 PM (Friday), David Jencks wrote:

>I disagree with everything you say. The current system has evolved as the
>solution to several earlier problems. Please suggest something concrete
>and explain its advantages, and in particular how it will reduce the
>maintenance effort needed by the jaybird developers.

Well, to do that I'd have to know what the earlier problems were that you
say were solved and how the current practice solves them.

Without that info, I would just say that de-coupling the downloading of
some JBoss code from the building of Jaybird is all that is required. I
would create a separate Ant target for doing this and NOT include it in the
normal Jaybrd build. Re-downloading should only be done during QA to insure
the latest Jaybird works with the latest JBoss.

My goal would be to have a system which allows a Java developer to download
a collection of source from a Jaybird site and build it without requiring a
CVS installation or anything else.

So, what is it I'm missing?