Re: cvs commit: jakarta-gump/project jakarta-ant.xml jakarta-commons.xml jakarta-taglibs.xml uddi4j.xml xml-crimson.xml xml-xerces.xml

Leo Simons wrote:
> Sam Ruby wrote:
> 
>> Nicola Ken Barozzi wrote:
>>
>>> What 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?

[...]

> For apache, the choice is rather easy to make: we generally trust all 
> asf committers to behave, and hence opening up the gump repo should not 
> present a problem. With the modest size of the new repo, it is also not 
> a big burden to keep a local copy of the gump repo updated. Once you 
> adjust to the idea "the project descriptor is in a different cvs", 
> there's virtually no difference.

[...]

> 
> which leads me to believe that the current setup is the best -- we do both:
> 
> Put the ASF project descriptors in the gump repo, and put the non-ASF 
> project descriptors elsewhere, where those projects have the option to 
> give the dependency magicians (like sam) access to their project 
> descriptor.
> 
> ---
> 
> To solve the centipede problem @ apache: simply make the gump repo a 
> requirment for building the project! That might also help 'edjucate' 
> ignorant developers (like, until recently, me) about the wonders and 
> importance of gump.

Checking out the Gump repo will help ignorant developers understand the 
wonders and importance of Gump?

Doesn't it also have to work? Make it easy to use and I can start to 
agree. That's what we want to do by making a system that automatically 
creates a profile for your local Gump, given the local projects.

> If I have to do
> 
> cvs co jakarta-avalon jakarta-gump
> centipede jakarta-gump/projects/jakarta-avalon.xml
> 
> instead of
> 
> cvs co jakarta-avalon
> centipede jakarta-avalon/project-descriptor.xml
> 
> well, I can live with that. 

So a user that gets a source distro of a project, he cannot compile 
without also downloading Gump?

> And if I can have the commands
> 
> cvs co jakarta-avalon
> ant jakarta-avalon/build.xml
> 
> result in the same thing, what's left to complain about? :D

Not with Centipede. With Centipede you *need* the descriptor. That's 
what it's all about. If you don't need it to build, it will never be 
kept updated.

So I reasonably *need* the descriptor to be with the project. I can 
synch with Gump, or viceversa, but in the end I need the descriptor in 
the project dir.

Honestly, Leo, imagine you're a Centipede developer. And you want to 
give an easy build system to your users. Do you really think that your 
proposal is a real solution? Look at it from my perspective too.

-- 
Nicola Ken Barozzi                   [email protected]
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------