On 8/18/01 1:25 AM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
>> So it hasn't occurred to you to use the descriptors in Gump, or help with
>> the ones that are in Gump already? I asked to have information added that
>> would allow Gump to work and provide the information for project
>> dependencies for building. I guess you missed that message. I started down
>> the same path, redoing the descriptors, and decided it was best to work with
>> Gump in the context of Alexandria. They have been working on the idea of a
>> project descriptor and a DTD for one for quite a long time.
>
> Like I said - I only got into and out of the conversation. And Gump and
> JJAR do not have the same functionality.
The crux of my argument is that many build tools will need project
information in order to satisfy requirments. The descriptors present in Gump
might not satisfy all requirements at present but they clearly can.
> Since JJAR needs richer
> version/dependency information, I thought that JJAR could be integrated
> with Gump to provide that info, removing Gump's need to maintain it. I
> had Sam's attention for a little while on this issue :)
All project information should be stored together.
> Gumps descriptors as I see them now still have no information about
> version, and specific version dependencies, which are important to JJAR.
As I've stated, repeatedly now, is that I asked that this information be
added to the project descriptor so that it would satisfy the requirements of
building a project.
> This I think reflects gump's purpose, which is version-blind
> cross-project build testing.
Gump's purpose as a building tool, but the project descriptors were a start
that met the needs of Gump but in the context of Alexandria (where gump
resides) the thought has always been to create a comprehensive description
for a project.
> JJAR and Gump will have some intersecting needs (dependency) and some
> orthogonal needs such as tool specific information (for each) and JJAR
> needs version by version dependency information.
My specific concerns are not for the various tools that can draw upon the
project information but the project information itself. Don't take Gump so
literally. It is what it is because of busy schedules, Sam has tried to get
a comprehensive description going as I recall a meeting at ApacheCon with
Jeff but Sam has really been the only one keeping the fire going as long as
I can remember.
>>
>> And you've already asked other projects to make descriptors completely
>> ingoring what's in Gump?
>
> Why would/could I do that? JJAR is just a sandbox experiment - we are
> trying to see if it's worthwile doing this, and people are interested in
> participating.
I was just piping up because I didn't want to see the experiment produce a
duplicate set of descriptors and than when they were equal having the 'we
have a set too so why should be get rid of ours' type debate. I'm just
trying to make sure that the Gump descriptors get worked on.
> What's in gump doesn't seem to do the trick.
Only because no one has put it in there, no one is stopping you we already
agreed that it would be wise to add any information a project might need.
>> Putting aside the fact that Sam and Jeff have been
>> trying to get a DTD going?
>
> A DTD for gump?
Yes, a thorough description of some sort.
>> Use what's already in place, in the context of
>> the project that has been trying to deal with these issues?
>
> I think it was pretty clear what I said. Gumps purpose was different
> than JJAR. Since JJAR would need a richer dependency/version map, I
> thought it cool to try to work with Gump and provide that info...
If you want to work with Gump than work on the descriptors so that they can
be used by any build tool that requires project information.
> geir
>
>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
