commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Colebourne <>
Subject Re: [fileupload] Remove commons-io dependency
Date Tue, 23 Aug 2005 19:04:00 GMT
Craig McClanahan wrote:
> 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.

I agree, svn:externals is clever, but copy-and-paste with comments will 
actually work better.

I am not a [fileupload] maintainer, so cannot -1 or force this issue. 
All I can do is try to persuade the actual maintainers that this 
dependency is not in your users best interests.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message