At 12:57 13/4/01 +0200, Ceki Gülcü wrote:
>>Gump does that by overriding properties (same as a build.properties file
>>does in the proposed approach).
>
>Build.properties in the proposed approach? Doesn't compute.
the library project uses build.properties where the rest of the world uses
.ant.properties to hold user specific, workspace specific and project
specific settings. In these settings you can locate position of specific jars.
>> Given that you can make it work without
>>JARs in CVS, let's turn the question around - what does it buy you to have
>>them there?
>>
>>Yes, it's nice to newbies to have the defaults set up to minimize the
>>effort of trying things. But that can be accomplished in other ways,
>>without the disadvantages.
>
>You are suggesting that users download the necessary dependencies using a
mechanism other than CVS. Right? While that is certainly reasonable it is
not clear if any fundamental issues are solved by this approach.
The people who advocate binaries in CVS do so for ease of use. If CJAN were
in place now it would be just as easy to use that rather than binaries in
CVS. Hence no need for the binaries.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
