You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gilles Sadowski (Jira)" <ji...@apache.org> on 2021/06/03 18:35:00 UTC

[jira] [Commented] (MATH-1587) Break "legacy" codes into several modules

    [ https://issues.apache.org/jira/browse/MATH-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356646#comment-17356646 ] 

Gilles Sadowski commented on MATH-1587:
---------------------------------------

A module {{commons-math-legacy-core}} was created for low-level functionality on which several packages in module {{commons-math-legacy}} depend.

Further modularization of module {{commons-math-legacy}} would be a tedious (and perhaps pointless) exercise given the cyclic dependencies of the packages there.

Improvement is likely to come only from refactorings aimed at fixing design issues identified over the years.

> Break "legacy" codes into several modules
> -----------------------------------------
>
>                 Key: MATH-1587
>                 URL: https://issues.apache.org/jira/browse/MATH-1587
>             Project: Commons Math
>          Issue Type: Sub-task
>            Reporter: Gilles Sadowski
>            Priority: Major
>              Labels: cyclic, dependencies, refactor
>             Fix For: 4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Splitting the {{commons-math-legacy}} module would help clarify the dependency relationships between the various functionalities of the library (towards removing unnecessary cyclic dependencies).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)