I would have really liked to see the permgen related errors looked into before the release was made...

Right now the only thing I can do to reliably build openejb 2.2 is to disable tests from running, otherwise these tests seem to fail randomly with permgen errors (even when using -XX:MaxPermSize=128m).

I just hope that this won't end up biting us down the line.

--jason


On 12/14/06, David Blevins <[EMAIL PROTECTED]> wrote:

Just want to explicitly state.  All community members are encouraged
to vote!  Even if you've yet to submit your first patch :)

-David

On Dec 13, 2006, at 6:44 PM, David Blevins wrote:

> All,
>
> The release is cut and awaiting your vote!  All the files are
> available in a staging area in my home dir on people.
>
> http://people.apache.org/~dblevins/stage/org/apache/openejb/
>
>    itests-2.2-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>    modules-2.2-incubating (jar,source,javadoc,pom){asc,md4,sha1}
>    openejb-2.2-incubating (jar,source,javadoc,pom){asc,md4,sha1}
> openejb-axis-2.2-incubating (jar,source,javadoc,pom) {asc,md4,sha1}
>    openejb-builder-2.2-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
> openejb-corba-2.2-incubating (jar,source,javadoc,pom) {asc,md4,sha1}
>    openejb-corba-builder-2.2-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
> openejb-core-2.2-incubating (jar,source,javadoc,pom) {asc,md4,sha1}
>    openejb-itests-core-2.2-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
>    openejb-pkgen-builder-2.2-incubating (jar,source,javadoc,pom)
> {asc,md4,sha1}
> openejb-yoko-2.2-incubating (jar,source,javadoc,pom) {asc,md4,sha1}
>
> All jars contain DISCLAIMER, LICENSE, and NOTICE.  Each binary jar
> is also accompanied by source, javadoc, pom and all are signed, md5-
> ed, and secure-hashed.  Keys file available here:
>
>    http://people.apache.org/~dblevins/stage/org/apache/openejb/KEYS
>
> Svn tag is here:
>
> http://svn.apache.org/repos/asf/incubator/openejb/tags/ openejb-2.2/
>
> Here's my +1!
>
> -David
>
>




--
Thanks
- Mohammad Nour

Reply via email to