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]

Nicola Ken Barozzi wrote:

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?

well, yeah. You need to be aggressively slamming 'em on the head with it, and then putting it within their line of sight. I had a filter on '[GUMP]', sending the messages to a special folder marked 'need-to-fix' and with a red font. Didn't actually work. Verbally hit me on the head with something and I'll work on it though (thanks Sam :).

Doesn't it also have to work?

Nicola, I'm really not trying to make your life harder, or make your job on centipede more difficult. Really. But fact-of-the-matter, right now, and for the past few months, the avalon peeps (including you and me) have been terrible at maintaining gump descriptors (or even the build process), and until I see things work differently (I've been trying) I'm thinking along the same lines Sam is.

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.

sounds good to me. More work, better results :D

I'm just being a real pragmatist: I need a fortress release (that's one of the packages in avalon-excalibur that doesn't work) in a few weeks, and I'd like a few nightly builds to start testing.

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?

IIUC, something that could work right now is copying the gump descriptor into the base dir of the source distro, and putting in place a different '.properties' file or something like that?

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

btw, my idea was that build.xml would check out gump and centipede, acting as a 'bootstrap'. Should be doable, no? ie something like:

<project default="main">
<target name="main">
<cvs checkout="${centipede}" repo="${krysalis}"
dir=".."/>
<cvs checkout="${gump}" repo="${jakarta}"
dir=".."/>

<exec script="../${centipede}/bootstrap.sh"/>
<cent/>
<gump/>
</target>
</project>

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?

well, no (and it's not to be taken as a proposal ;). But it is the easiest thing that could possibly work (in that I could probably set it up). I'm totally supportive for real solutions, but I'm okay with hacky solutions until those real solutions arrive (to paraphrase Berin "waiting until the next release of [the maven and centipede] projects").

Look at it from my perspective too.

I am, I am!

cheers,

- Leo




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>