Si Chen wrote: > I don't know about the particulars of the commons-fileupload library, > but the problem with the bsf is that it interfered with the currently > used jpublish. If you can supply an upgrade combination of bsf and > jpublish that still works, I think that should work for me (and > hopefully the other committers as well.) Otherwise, given how little > the bsf library is actually used in the core ofbiz applications and > framework, it made little sense to break existing functionality just to > get a newer version of it.
Yes, well, there is a patch from someone else from 2004(see the bug) that fixes that. And that patch was never applied. It's all well and good to provide patches, but if they never get applied by those in charge, it makes those that provide said patches reluctant to provide more in the future. > In general the goal of updating the libraries is a good one, but in my > opinion it has to be well-tested so that the functionality of the core > project is not compromised. So, instead of going forward, fixing jpublish, you'd rather stay back? Why does one person have to do all the work at fixing something?
