At 7:38 -0500 6/4/03, Glenn Nielsen wrote:
Was this really necessary? The email below went to both the commons-dev and
tomcat -dev lists. If Remy was pointing the finger at anyone, it was at his
fellow Tomcat Developers. Thats how I interpreted it.
Martin has been busting his tail trying to get
FileUpload.setRepositoryPath(String) and FileItem(String) were removed from
the fileupload RC 1 release, which breaks the Tomcat 4.1.x and 5.0.x build.
The first method has no apparent replacement (but I didn't try to dig
around).
This is clearly an unacceptable situation from the Tomcat perspe
One last note: IMO, as a rule (and esp in the commons), you should make
every effort to avoid breaking the API between a beta and a final.
FileUpload did not go final, if went to RC1. Changes between RCs and final
could be considered inappropriate but not from beta to RC.
See the Release Types
Glenn Nielsen wrote:
Martin Cooper wrote:
Get your own act together, Tomcat developers, before you start pointing
the finger at those of us who really try hard to maintain compatibility
across Jakarta projects.
Was this really necessary? The email below went to both the commons-dev
and
tomcat -d
Martin Cooper wrote:
I posted a patch to the Tomcat-Dev list yesterday which should fix this
problem. Apparently, nobody on the Tomcat-Dev list paid any attention to
my post. The methods in question have been deprecated for some time.
I have not seen the patch email on tomcat-dev. Perhaps its in t
The attached works for me (against commons-fileupload HEAD). I didn't do
anything about it since I wasn't sure which version of fileupload we were
targeting.
- Original Message -
From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>; "Jakarta
Commons
