Sorry for the slow response -- commitments on Tomcat yadda yadda (Tomcat
4.0 final will be in a couple of weeks :-).
Such issues really need to be addressed in both developments -- in the
Struts copy of these classes for a 1.0.1 release, and here for the
corresponding commons versions used in Struts 1.1.
I will commit the changes (in both places) for this one tomorrow.
Craig
On Tue, 4 Sep 2001 [EMAIL PROTECTED] wrote:
Date: Tue, 4 Sep 2001 21:04:40 -0700
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Fw: Fixing bugs in Struts code moved to Commons
I posted this to struts-dev a week ago and received no response, so I
figured it's time to see what the folks over here in jakarta-commons think.
:-)
--
Martin Cooper
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 28, 2001 8:59 PM
Subject: Fixing bugs in Struts code moved to Commons
There is at least one bug (#2494) in the Struts bug database which is in
code moved to Commons after the Struts 1.0 release. To be fixed properly,
the change should be made both in the Struts code base (for Struts 1.0.1)
and in the Commons code base.
How should we manage this type of issue? I assume not all Struts
committers
are also Commons committers (I don't think I am), so I can think of a
couple
of options:
1) Fix the Struts bug and enter a new bug report against the Commons code.
2) Have only committers on both projects address these bugs.
I can see pros and cons to both options.
Thoughts?
--
Martin Cooper
