[
https://issues.apache.org/jira/browse/JCR-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570455#action_12570455
]
Thomas Mueller commented on JCR-1395:
-------------------------------------
I also like to keep the number of dependencies as low as possible. Dependencies
mean additional complexity because it means more work for a Jackrabbit user
(installation), and because he could depend on a different version of the same
library. This can be solved by 'refactoring' the package name of the dependency
(complex) or using special class loaders or OSGi (also very complex).
I would prefer if we maintain our own utility classes. It is more work and also
a bit risky (I don't think it's that bad actually), but easier for the user and
less complex. One extreme is to have no dependencies (only depend on the JDK).
I know some view it as 're-inventing the wheel' and they are right.
If we don't want to maintain our own utility classes (and I think we didn't do
a very good job at that so far), using Commons IO is a good solution. It's much
better than copy & paste source code. So adding Commons IO is OK for me.
> Use Commons IO 1.4
> ------------------
>
> Key: JCR-1395
> URL: https://issues.apache.org/jira/browse/JCR-1395
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
> Priority: Minor
> Fix For: 1.5
>
> Attachments: io.patch
>
>
> Commons IO contains a number of utility classes and methods for working with
> files and streams. Many of those utilities would be quite useful in
> Jackrabbit, so I'd like to introduce commons-io 1.4 as a dependency to
> jackrabbit-core.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
