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.
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.
On Nov 1, 2006, at 12:52 PM, Adam Heath wrote:
Recently, I filed a bug(OFBIZ-401), to update bsf.jar to something
more
modern. This was backed out, as ofbiz makes use of an ancient
jpublish
that also uses the older bsf.
Just recently, I had another case occur, with an old library.
commons-fileupload is also very old, and the current version has an
api
change.
I find it very annoying that such old stuff is still in use in ofbiz,
especially if a release is pending. Any application integrator
that is
going to use ofbiz is going to want to use more modern libraries, but
will not be able to, as all the interdependent code in ofbiz is using
older stuff.
Can we make it a release goal to update the libraries to something
much
more modern? I'm willing to help produce a list, giving each library,
the version in use, the upstream location, and the most recent
version.
Best Regards,
Si
[EMAIL PROTECTED]
