Hi,
Thanks for reporting this problem.
This is an embarrassing bug. Is the problem already identified? If
this is a Geronimo regression, then it seems to me that we need to be
improve our testing approach. For instance, along with each bug fix,
I would expect the addition of new tests to prevent future
regressions. Along with each new features, I would expect good tests
proving that the feature works. And I would expect tests to be
committed at the same time than source tree changes and not after the
fact. If this is not a Geronimo issue, then I think my point still
stands.
When is 2.1.1 due? If it is in more than in 2 weeks, then I would
like a withdraw of 2.1.
Thanks,
Gianny
On 16/02/2008, at 2:12 AM, Jarek Gawor wrote:
Looks like I sent this to the wrong thread:
This is about: https://issues.apache.org/jira/browse/GERONIMO-3855
Hmm this seems bad. I was able to reproduce the problem on port 8443
only but _all_ portlets failed in this way. So the console is pretty
much unusable on port 8443. Can somebody else verify these findings?
Jarek
On Thu, Feb 14, 2008 at 1:30 PM, Jacek Laskowski
<[EMAIL PROTECTED]> wrote:
On Thu, Feb 14, 2008 at 8:47 AM, Lin Sun <[EMAIL PROTECTED]>
wrote:
P.S. sorry for trying these late - i just got back from a long
long leave...
No need to worry. Do whatever you can and your time permits. Even
late-runners have something to say and their voice counts. Report
any
issue you run across so it gets fixed in the upcoming releases if
2.1
is already out.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
