commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allen Servedio <>
Subject Re: [BeanUtils] When will 1.7 be released?
Date Wed, 11 Feb 2004 13:03:02 GMT

I thought what you were suggesting was to replace the 
commons-beanutils.jar file that comes with Struts with the 1.7 
version...? It has been so long since I last looked at this that I 
forget if that is one of the things that I tried. Anyway, I am going to 
try it and will let you know if that took care of things. I would have 
done it already, but I have a pretty limited amount of time that I can 
spend on these types of things (though, I should deal with it this month).

Thanks again for your advice. Sometimes it is the simple solutions that 
are most often over looked ;-)


now I've re-read my reply, I'm no longer sure what i was suggesting...

- robert

On 6 Feb 2004, at 21:37, Allen Servedio wrote:

> Hi Robert,
> Thanks again for your reply. I'll do as you suggest.
> Allen
> On 29 Jan 2004, at 13:25, Allen Servedio wrote:
>> Hi Robert,
>> Thanks for responding (I get this in digest version, so I put your 
>> reply below)!
>> Actually, I do not need a full release; but I think that the Struts 
>> team does.
> there is a considerable overlap between the teams. i'd hope that 
> people would shout if this really were the case :)
>> I was using one of the release candidates with the intention of 
>> upgrading when they released 1.1 (which they did). The release 
>> candidate used BeanUtils 1.7... BUT, their final 1.1 release uses 
>> BeanUtils 1.6.1 (which makes sense, as they want to have all of the 
>> released code synced up). I did not realize this until quite a bit 
>> later and now I am stuck. I can't go to the released version of 
>> Struts 1.1 because I am using BeanUtilsBean, ConvertUtilsBean, and 
>> PropertyUtilsBean (which do not exist in BeanUtils 1.6.1).
> i'm not sure that i understand you problem. CVS HEAD should be 
> backwards compatible with 1.6.1 and so you should be able to drop it 
> in as a replacement, shouldn't you?
> IMHO (and i can only speak for myself) there are two major factors 
> preventing a new beanutils release.
> the first is finding someone on the pmc to volunteer to act as a 
> release manager. (but this isn't a big problem.)
> the second is doing the work required before we can commit to a 
> release. there's quite a lot of work to do (both in implementation and 
> design) but a shortage of development energy. i'm very glad to see 
> that yoav's stepped up. if some more people volunteered to take on 
> some development, then we'd probably get a lot closer a lot quicker.
> personally speaking, beanutils will not be a high priority until 
> betwixt is much closer a release.
> - robert
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Allen M. Servedio
Software Engineering Consultant (Matrix Resources)
ITD (Information Technology Department) [formerly AIST] 
GTRI (Georgia Tech Research Institute)
404-385-0498 -

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message