You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Michael Baessler <mb...@michael-baessler.de> on 2007/11/29 14:46:37 UTC

uimaj-2.2.1-03 ready for testing

I have uploaded the latest release candidate for release 2.2.1 to
people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03

So we can start testing with this level.

--Michael


Re: uimaj-2.2.1-03 ready for testing

Posted by Michael Baessler <mb...@michael-baessler.de>.
Michael Baessler wrote:
> I have uploaded the latest release candidate for release 2.2.1 to
> people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03
>
> So we can start testing with this level.
>
> --Michael
>
During the release testing, please also check all issues that are in 
"resolved" state if they can be closed.
The issue reporter have to close the resolved issues if they are fixed.

-- Michael

Re: uimaj-2.2.1-03 ready for testing

Posted by Thilo Goetz <tw...@gmx.de>.
We have discovered two minor issues since this level
was built: one missing header (doesn't affect testing)
and one failing test case (ok on windows).  If you're
not running the test cases, or you're working on windows,
you're still good to test with this level.

--Thilo

Michael Baessler wrote:
> Michael Baessler wrote:
>> I have uploaded the latest release candidate for release 2.2.1 to
>> people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03
>>
>> So we can start testing with this level.
>>
>> --Michael
>>
> I created the level with the latest SUN Java 5 JVM (1.5.0_14).
> 
> -- Michael

Re: uimaj-2.2.1-03 ready for testing

Posted by Michael Baessler <mb...@michael-baessler.de>.
Michael Baessler wrote:
> I have uploaded the latest release candidate for release 2.2.1 to
> people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03
>
> So we can start testing with this level.
>
> --Michael
>
I created the level with the latest SUN Java 5 JVM (1.5.0_14).

-- Michael

Re: uimaj-2.2.1-03 ready for testing

Posted by Michael Baessler <mb...@michael-baessler.de>.
The message:

'tar: A lone zero block at *'

is just a warning and can be ignored. All content is extracted 
correctly. The reason for the message is that newer tar versions expects 
two empty records
marking the end of the archive but it seems that our Maven build only 
creates one.
I tested with the latest Maven version 2.0.8 but it seems that the error 
still occurs.

I also found the following Maven issue:
http://jira.codehaus.org/browse/MNG-2762

-- Michael

Michael Baessler wrote:
> Michael Baessler wrote:
>> I have uploaded the latest release candidate for release 2.2.1 to
>> people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03
>>
>> So we can start testing with this level.
>>
>> --Michael
>>
> I seems that we have some issues with the tar.gz archives...
>
> With an older version of GNU tar (1.13) all works fine. With a newer 
> version (1.15) we got errors while decompressing the archive.
> Can anyone else please verify that?
>
> Thanks Michael


Re: uimaj-2.2.1-03 ready for testing

Posted by Thilo Goetz <tw...@gmx.de>.
Same problem with 1.18, btw.

Michael Baessler wrote:
> Michael Baessler wrote:
>> I have uploaded the latest release candidate for release 2.2.1 to
>> people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03
>>
>> So we can start testing with this level.
>>
>> --Michael
>>
> I seems that we have some issues with the tar.gz archives...
> 
> With an older version of GNU tar (1.13) all works fine. With a newer
> version (1.15) we got errors while decompressing the archive.
> Can anyone else please verify that?
> 
> Thanks Michael

Re: uimaj-2.2.1-03 ready for testing

Posted by Michael Baessler <mb...@michael-baessler.de>.
Michael Baessler wrote:
> I have uploaded the latest release candidate for release 2.2.1 to
> people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03
>
> So we can start testing with this level.
>
> --Michael
>
I seems that we have some issues with the tar.gz archives...

With an older version of GNU tar (1.13) all works fine. With a newer 
version (1.15) we got errors while decompressing the archive.
Can anyone else please verify that?

Thanks Michael