On 8/21/01 11:09 PM, "Sanders" <[EMAIL PROTECTED]> wrote:
> Are we making sure that the version info contains all types of
> information, ie not just the version of dependency x, but also the fact
> that for version 1.0 the dependency on x didn't even exist?
We can take anything into consideration, I've simply added version="x" to
the turbine descriptor. It doesn't affect the way gump works, but you raise
a valid question and is another thing to think about when making a project
descriptor dtd/schema.
> Scott Sanders
>
>> -----Original Message-----
>> From: Jason van Zyl [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, August 21, 2001 7:55 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: [gump] adding version info
>>
>>
>> On 8/21/01 10:05 PM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
>>
>>> Our discussion revolved around making JJAR work against the gump
>>> information repository rather than it's own information repository.
>>>
>>> My personal belief is that either
>>>
>>> 1) Gump should use JJAR to get dependency information.
>> Using tools is
>>> good.
>>
>> I think that all of a projects information should be stored
>> in a single
>> location. Gump has full inter-project dependencies, but what
>> it lacks is the
>> version info to build a release with stated versions of
>> packages, and the
>> project descriptors don't currently state their latest version. A few
>> additions and building a project with specific versions of
>> packages will be
>> possible. This info will also be enough for a JJAR like task
>> to assist with
>> a build.
>>
>> I am fully aware of the need for version info because I plan
>> to use Gump to
>> build distributions of the TDK in a reliable way that will
>> let any Turbine
>> developer who wants to participate managing releases do so in
>> a consistent
>> fashion. We obviously must use stated versions of tools. This
>> would allow a
>> rigourous build of a distribution that would be consistent
>> across machines.
>>
>>> 2) If Gump doesn't want to depend on external tools and
>> must define its
>>> own dependency information, then it should make that
>> dependency set free
>>> of any gump specific schema structure or data, so that it
>> can be shared
>>> as widely as possible and let all tools that use it (gump included)
>>> evolve in their own way w/o affecting the others.
>>
>> Again I see it as project information as a whole, if you have a better
>> layout for dependencies I think it should be added the
>> descriptors in the
>> gump repository. I don't see them as gump descriptors. I see
>> them as project
>> descriptors that gump utilizes. I think that many, many tools
>> can use these
>> descriptors JJAR among them.
>>
>>> I have a whole bunch of reasons for both, but I won't bore
>> y'all with
>>> them.
>>>
>>> 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]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
