DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31477>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31477





------- Additional Comments From [EMAIL PROTECTED]  2005-10-03 09:34 -------
(In reply to comment #2)
> (In reply to comment #1)
> > If that's the case, then my apologies: it's too late to fix it now.

Yes, it is true. It's documented in the BeanUtils FAQ:
  http://wiki.apache.org/jakarta-commons/BeanUtils/FAQ

> 
> Will it be changed in the soruce so at least the next version won't have the
> same problem? This caused me an hour of headache because I am working with a
> commons-beanutils.jar that declares it is 1.6 when it is in fact 1.7. You can
> imagine the trouble my debugger had when I had associated the 1.6 source code
> with that JAR...

As the FAQ notes, this won't happen again now that Maven is being used for
building BeanUtils. However as the beanutils wiki page states, BeanUtils is
unlikely to have any more releases - at least there are no active maintainers at
the current time.

> 
> Also, why is there no 1.7 version listed in Bugzilla for the Bean Utils 
> component?
> 

It appears that bugzilla only provides release#s per product, not per component.
And commons is represented as a product with the individual libs as components.
I suppose we could ask for someone with bugzilla admin rights to add 1.7/1.8/1.9
options to the list...

JIRA could be used for bugtracking instead, but the migration would be a lot of
work and given the generally dormant state of beanutils just isn't going to 
happen.



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to