Most of the test cases are working now - ready for a beta release?

Allen Servedio <[email protected]> Sat, 2 Jan 2010 20:01:32 -0500
Newsgroups gmane.comp.java.mx4j.devel
Message-ID <[email protected]>
--===============8200582394272899181==
Content-Type: multipart/alternative; boundary=001485f5b1864383ca047c38257c

--001485f5b1864383ca047c38257c
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have most of the test cases passing for all subprojects now (including
some that were on the exclude test list). There are a couple of JSR 160 ones
that are resisting my efforts (not sure if they are important as they are
failures on shutting down the ORB, but maybe there is something wrong...).

In any event, I think we are close to being able to release the beta version
now. I think the pom files can be optimized a bit more (esp. since this only
works with Maven 2.0.10 or lower) to make them easier to push through the
release process AND to do an actual release we would have to update the
version number to have -SNAPSHOT.

But, other than that minor house keeping, I think we can push a beta release
out unless someone thinks there are some other set of tests that need to get
added first?

Thoughts?

Also, Simone, if you are monitoring this, I might need a bit of help pushing
a release for this assuming you think it is ready for one...

Thanks!
Allen

--001485f5b1864383ca047c38257c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I have most of the test cases passing for all subprojects now (i=
ncluding some that were on the exclude test list). There are a couple of JS=
R 160 ones that are resisting my efforts (not sure if they are important as=
 they are failures on shutting down the ORB, but maybe there is something w=
rong...).<br>
<br>In any event, I think we are close to being able to release the beta ve=
rsion now. I think the pom files can be optimized a bit more (esp. since th=
is only works with Maven 2.0.10 or lower) to make them easier to push throu=
gh the release process AND to do an actual release we would have to update =
the version number to have -SNAPSHOT. <br>
<br>But, other than that minor house keeping, I think we can push a beta re=
lease out unless someone thinks there are some other set of tests that need=
 to get added first?<br><br>Thoughts? <br><br>Also, Simone, if you are moni=
toring this, I might need a bit of help pushing a release for this assuming=
 you think it is ready for one...<br>
<br>Thanks!<br>Allen<br><br><br>

--001485f5b1864383ca047c38257c--


--===============8200582394272899181==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
--===============8200582394272899181==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mx4j-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mx4j-devel

--===============8200582394272899181==--