On 8/18/01 12:32 AM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
>> I did originally when I did the first version of maven, but as they changed
>> so much all the time I started working with the descriptors in gump and
>> that's turned out to be the better route. Sam keeps them up-to-date and now
>> I try to do the same.
>>
>> I gave up on the idea of redoing them and am working with what sam started.
>
> I meant 'you' in the collective sense, not personally - I have been in
> and out of things and saw a long thread between you and sam discussing
> changing and normalizing the descriptors.
>
> To get back to the issue, I don't think that gump is the right place for
> them - I think that the right place for them is in the projects
> themselves. I mean, each project is the best authority on what their
> dependencies are.
If you actually looked at the descriptors, you'll 'href' for the project
descriptor. Sam kept this notion in mind, and I agree that it would be best
for a project to maintain its own project information but having them stored
all over the place might not be practical. I would definitely like to try it
with gump.
> Further, JJAR isn't intended to be in any way a competitor or
> replacement of Gump - Gump fills a unique role in what it does, the
> cross-building of projects against each other, and there is no need to
> replace it.
No but you are duplicating the project descriptors. Gump has started this
and, whether they are distributed or not eventually, has the most
comprehensive set of project descriptors so far.
> JJAR is meant to be something entirely different - primarily a
> 'CPAN'-ish system for Java, to make getting jars easy and painless.
> No
> more jars in CVS, and automatic fetching of dependencies. Recently I
> added the notion of 'project repository kept by the project' and want to
> see how it works. So far, pretty good in the toy example, namely the
> Veltag JSP taglib in Velocity uses it's own repository descriptor for
> it's build process, fetching the jars it needs (servletAPI and Velocity)
> from the central repository. Dom4j is (hopefully) working on theirs, so
> we can test this out with something more substantial (no one cares about
> Veltag...). I will ask Jason Hunter if he can (or I can for him ) do
> the same for JDOM.
>
> The point of sharing this information with Gump is that it solves the
> problem for both tools, and further does it in a way that allows the
> projects both within and outside of Jakarta to be involved by
> maintaining their own projects' repository descriptor as well as their
> released jars.
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.
And you've already asked other projects to make descriptors completely
ingoring what's in Gump? Putting aside the fact that Sam and Jeff have been
trying to get a DTD going? Use what's already in place, in the context of
the project that has been trying to deal with these issues?
> Figured I would ask...
>
> 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]
