struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <craig...@apache.org>
Subject Re: cvs commit: jakarta-struts/src/share/org/apache/struts/config ConfigRuleSet.java
Date Sat, 21 Dec 2002 18:54:51 GMT


On Sat, 21 Dec 2002, Martin Cooper wrote:

> Date: Sat, 21 Dec 2002 10:49:19 -0800 (PST)
> From: Martin Cooper <martinc@apache.org>
> Reply-To: Struts Developers List <struts-dev@jakarta.apache.org>
> To: Struts Developers List <struts-dev@jakarta.apache.org>
> Subject: Re: cvs commit:
>     jakarta-struts/src/share/org/apache/struts/config ConfigRuleSet.java
>
>
>
> On Sat, 21 Dec 2002, Craig R. McClanahan wrote:
>
> >
> >
> > On 21 Dec 2002 martinc@apache.org wrote:
> >
> > >   Update to avoid the use of deprecated Digester methods. Some deprecated
> > >   methods are still used, but their replacements are not yet available in
> > >   a released version of Digester. We don't want to depend on a new Digester
> > >   release just for this, so leave them for now.
> >
> > Actually, our general rule has been that a final release of Struts 1.1
> > *must* depend on updated final releases of the commons components.  There
> > are other dependencies already on things that have been fixed in the
> > nightly commons builds; we should assume that in cases like this.
>
> Yes, I realise that we need to depend on appropriate final releases of
> Commons components in 1.1 Final. What I didn't want to do was *require* a
> new release of Digester for Struts *only* to fix deprecation warnings. I
> don't track Digester as closely as I used to, so I don't know if there is
> anything else post-1.3 that is needed for Struts.
>

There are some Digester bugfixes that we want.  There's *lots* of stuff in
beanutils that we need.

> > In the particular case of beanutils and digester, there is movement
> > towards releases in the short term -- which is why I've been focused on
> > the outstanding bugs there as well as in Struts itself.
>
> Then perhaps we should go ahead and fix the remaining deprecation warnings
> from Digester sooner rather than later?
>

Yep.

> > RELEASE MANAGER NOTE - you'll find that I tagged the Commons trees with a
> > CVS version tag for the betas, so that one can reliably determine which
> > commons code was included.  I suggest we do the same for b3.
>
> I did this for b2, and plan to do the same for b3. I also intend to remove
> commons-services in b3, but leave the source in contrib.
>
> Talking of b3, I'm still waiting for feedback from the committers before I
> post a revised release plan...
>

I've got a Christmas present shopping trip yet to do today (just-in-time
design pattern :-), but otherwise plan to spend some time this weekend on
assessing where we are and cleaning up what I can.  But, in general, a
good beta3 release would be a nice Christmas present to give the rest of
the world.

> --
> Martin Cooper

Craig


--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@jakarta.apache.org>


Mime
View raw message