[
https://issues.apache.org/jira/browse/IMAGING-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743471#comment-17743471
]
Gary D. Gregory commented on IMAGING-309:
-----------------------------------------
There is no rationale in the description, there is not even a single example.
Dependency for dependency's sake is the kind of circular argument that is not
rational IMO. Let's see how much code duplication introducing this dependency
would remove, then we'll have something to talk about.
> Depend on "Commons Numbers"
> ---------------------------
>
> Key: IMAGING-309
> URL: https://issues.apache.org/jira/browse/IMAGING-309
> Project: Commons Imaging
> Issue Type: Wish
> Components: imaging.common.*
> Reporter: Gilles Sadowski
> Priority: Trivial
> Labels: dependencies, maintainability, robustness
> Fix For: 1.0
>
>
> It would make sense for high-level components such as [Imaging] to depend on
> lower level utilities developed within "Commons", such as [Numbers], where
> # changes in dependencies can be controlled by the same team, and
> # JAR hell is _not_ an issue (as per the project's policy on BC).
> Both [Imaging] and [Numbers] would benefit from such an ecosystem:
> * The low-level component is put to test in an actual use-case.
> * The high-level component does not need to maintain lower-level utilities.
> Motivation: IMAGING-285
> At the time, it might not have made sense to depend on a component like
> Commons Math (with its ever expanding code base) just for its {{Fraction}}
> class. Nowadays however, "Commons Numbers" provides the functionality in a
> dedicated [maven
> module|https://mvnrepository.com/artifact/org.apache.commons/commons-numbers-fraction/1.0].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
