Well, the binary dist is currently getting built into build/bin/commons-collections-3.2-dev and the source distribution into build/src/commons-collections-3.2-dev
This is all neatly setup then for the zip target. Another reason for moving it was to avoid creating two build folder, which I reckon is a better layout. But then I didn't know about the nightlies dependency.
The best I can think of is to rename the collections dist target to gather, and make dist copy the folder from its current location.
Stephen
----- Original Message ----- From: "Craig McClanahan" <[EMAIL PROTECTED]>
On Sat, 12 Feb 2005 18:33:06 -0000, Stephen Colebourne <[EMAIL PROTECTED]> wrote:That got changed ages ago IIRC.
Can your scripts handle an ant property override to change the output directory, or must we change the checked in script.
Stephen
The part of the processing that fails due to this is a shell script that renames the "dist" directory to something like "commons-collections-YYYYMMDD" before tarring and zipping it up, then renames it back again. I can probably hand code an exception for collections, but it's not even obvious (from looking at the directory structure) what stuff should go into the "binary" tar or zip files.
Is there a particular reason that your build script is unique (across Commons Proper and Commons Sandbox) in this respect?
Craig
----- Original Message -----
From: "Craig McClanahan" <[EMAIL PROTECTED]>
> The nightly build script expects that the output of "ant dist" will
> show up in a "dist" subdirectory, like it does for every other commons
> package. That no longer seems to be the case for [collections].
>
> Craig
>
>
> On Sat, 12 Feb 2005 00:29:17 -0500, Phil Steitz <[EMAIL PROTECTED]> > wrote:
>> The nightlies seem to be failing for [collections], but the ant build
>> works fine for me. Any ideas why the nigthlies are failing?
>>
>> Phil
>>
>> ---------------------------------------------------------------------
>> 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]
>
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
