New artifacts just posted.  p.a.o has been really slow today.

It looks like the issue is that I grabbed the tarball after executing
build-mac.sh, which apparently builds up the tarball without the modeler
binaries.  I think I made this same mistake when posting the 3.0M2 binaries.

I'll have to make a mental note not to do that any more.

-- 
Kevin


On 1/28/08 10:15 AM, "Andrus Adamchik" <[EMAIL PROTECTED]> wrote:

> 
> So what about missing Modeler in tar.gz?
> 
> Andrus
> 
> On Jan 28, 2008, at 5:08 PM, Kevin Menard wrote:
> 
>> They were built from the tag, including Tore's latest changes.
>> 
>> Everything was built from maven (I grabbed the output from the
>> assembly
>> step), save for the Windows version.  I manually created the ZIP after
>> untarring the tarball.  This is consistent with what I did for 3.0M2.
>> Unfortunately, I forgot to add a custom assembly step to automate
>> this, but
>> will do so in trunk.
>> 
>> -- 
>> Kevin
>> 
>> 
>> On 1/28/08 9:51 AM, "Andrus Adamchik" <[EMAIL PROTECTED]> wrote:
>> 
>>> Hi Kevin,
>>> 
>>> Thanks for taking a lead on the release. Just to doublecheck - the
>>> snapshots you posted are from the 3.0M3 tag?
>>> 
>>> Also the tar.gz version does not seem to include the Modeler. Was it
>>> built with Maven or in some other way?
>>> 
>>> Thanks,
>>> Andrus
>>> 
>>> 
>>> On Jan 28, 2008, at 4:30 PM, Kevin Menard wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> I've prepared binaries for the 3.0M3 release.  The are available
>>>> here:
>>>> 
>>>> http://people.apache.org/~kmenard/release/3.0M3/
>>>> 
>>>> In my own testing, everything worked fine with HSQLDB and PostgreSQL
>>>> 8.2 on
>>>> MacOS X.  Derby testing failed, but Tore discovered why and the
>>>> issue will
>>>> be addressed in trunk.  Windows testing failed, but I'm quite
>>>> confident it's
>>>> test environment related (line endings, path separators, etc.) and
>>>> the core
>>>> framework tests passed.
>>>> 
>>>> Please test out the binaries and then cast your vote.
>>>> 
>>>> This is my +1 (binding).
>>>> 
>>>> -- 
>>>> Kevin
>>>> 
>>>> 
>>> 
>> 
>> 
> 

Reply via email to