Any more thoughts on droping jetty assembly from 3.0.0 release? or I will go ahead to make the change and roll out 3.0.0 release...
+1 to drop Jetty release from 3.0.0 release for now.--On Mon, Jun 25, 2012 at 12:04 PM, Forrest Xia <email@example.com> wrote:
Echo Jarek's response here in dev list again:
So it looks like we have quite a bit of failures on Jetty. I guess we
either have to drop it from the release (if we want to release soon)
or try to fix it and delay the release. Thoughts?
My thought is to drop jetty release for 3.0.0 and roll out tomcat assembly asap. Any more thoughts about 3.0.0 release??--
On Sat, Jun 23, 2012 at 9:06 PM, Forrest Xia <firstname.lastname@example.org> wrote:
On Sat, Jun 23, 2012 at 12:57 AM, Kevan Miller <email@example.com> wrote:
On Jun 22, 2012, at 9:20 AM, Forrest Xia wrote:
> On Fri, Jun 22, 2012 at 8:36 AM, Forrest Xia <firstname.lastname@example.org> wrote:Forrest -- too much TCK information on a public list. TCK terms may be improving in the future. However, until then, we should not talk about test names, numbers of tests, etc.
> On Tue, Jun 19, 2012 at 10:42 AM, Forrest Xia <email@example.com> wrote:
> On Tue, Jun 19, 2012 at 9:47 AM, Jarek Gawor <firstname.lastname@example.org> wrote:
> How are things with Jetty? Some user emails gave me an impression that
> things don't look too good. If things with Jetty are looking bad then
> we should either consider dropping it from the release or delaying the
> release until we get it in shape.
> Some status consolidation here about Jetty assembly in 3.0 branch:
> 1. BV and DI tck all pass for jetty8-javaee6 assembly
> 2. JCDI and full profile execution just triggered, we will see some results after two days.
> JCDI tck against jetty8-javaee6 failed most of the cases.
> Jetty assembly results:
> Tests 37068
> Passed 23616
> Failed 13452
OK, got it, sorry for that.