On 8/22/05, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > Martin's valid points aside, if you just want to copy the classes from IO, > you can use external in SVN. >
If we follow the path to fork those classes, it would be better to just rename them back into the org.apache.commons.fileupload package space, and dispense with any notion that the classes would remain in sync. We couldn't do that with the beanutils/digester dependency on collections, because there were some implementation specific APIs (incorrectly) baked in to the public API. Using SVN externals for this is a cute hack to avoid forgotten cut-n-paste edits, but it doesn't address the process issues of release timing or ensure that (for example) someone from one of the cooperating projects would not change the code in incompatible ways, having no clue that the SVN external trick was being used, and would unknowingly break somebody else. > --- Noel Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
