Sam Ruby wrote:
Nicola Ken Barozzi wrote:
Ok, getting real, what you say and what I say are IMHO both notable features that fill real needs. Needs are never in discord, implemantations are. Let's see how we can fix implementations to make all needs satisfied.
+1What about making Gump commit the latest descriptors in its CVS at every run? With the possibility of not-synching for some projects in case ASF developers want to try and fix the Gump version?
Let express my root need or requirement, then we can discuss implementations.
For projects I care about (and that's a *lot* of projects), I want the descriptors to *either* be actively maintained or someplace that bodewig, conor, Stephen, myself, and several others (hi leosimons and mpoeschl and mvdb and cmlenz!) can update.This is not your requirement, it's a Gump need. It's quite evident to all.
Your way of making Gump runs work is to have a deep knowledge aff all Jakarta codebases and fix them yourself.
My view is that the Gump descriptors are the base of the daily builds of a project, so that users will be *forced* to maintain most of it, or else the project won't compile.
These are the two *eithers* that you are talking about.
What we need to discuss is how we can make the second case work and still have the descriptors in Gump CVS. If you don't think that in this case it's needed, case solved.
My creating of a place where all ASF committers can update is one possible implementation.
Please take my view in account also, if you want.
And reply to my implementation proposal now that you made yourself heard.
Note: I had to rewrite this mail three times.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
