You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Nick Fortescue (JIRA)" <ji...@apache.org> on 2011/04/20 18:49:05 UTC
[jira] [Created] (MATH-560) Incorrect @Deprecated tags added to
no-args Solver constructors in org.apache.commons.math.analysis.solvers
Incorrect @Deprecated tags added to no-args Solver constructors in org.apache.commons.math.analysis.solvers
-----------------------------------------------------------------------------------------------------------
Key: MATH-560
URL: https://issues.apache.org/jira/browse/MATH-560
Project: Commons Math
Issue Type: Bug
Affects Versions: 2.2
Reporter: Nick Fortescue
Priority: Minor
During refactoring of the solvers, an @Deprecated javadoc comment was added to the no argument constructor for a number of Solvers, saying they would be removed for 3.0.
This is incorrect - there is no plan to remove those constructors. See the discussion on the user list on 2011-04-20. The @deprecated tag should be removed.
This causes deprecation warnings in previously compliant code, and should not.
This affects at least the following Solvers: MullerSolver, SecantSolver, NewtonSolver.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MATH-560) Incorrect @Deprecated tags added to
no-args Solver constructors in org.apache.commons.math.analysis.solvers
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MATH-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz updated MATH-560:
-----------------------------
Fix Version/s: 2.2.1
> Incorrect @Deprecated tags added to no-args Solver constructors in org.apache.commons.math.analysis.solvers
> -----------------------------------------------------------------------------------------------------------
>
> Key: MATH-560
> URL: https://issues.apache.org/jira/browse/MATH-560
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Nick Fortescue
> Priority: Minor
> Fix For: 2.2.1
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> During refactoring of the solvers, an @Deprecated javadoc comment was added to the no argument constructor for a number of Solvers, saying they would be removed for 3.0.
> This is incorrect - there is no plan to remove those constructors. See the discussion on the user list on 2011-04-20. The @deprecated tag should be removed.
> This causes deprecation warnings in previously compliant code, and should not.
> This affects at least the following Solvers: MullerSolver, SecantSolver, NewtonSolver.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MATH-560) Incorrect @Deprecated tags added to
no-args Solver constructors in org.apache.commons.math.analysis.solvers
Posted by "Gilles (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MATH-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilles resolved MATH-560.
-------------------------
Resolution: Fixed
Removed deprecations in revision 1157395.
> Incorrect @Deprecated tags added to no-args Solver constructors in org.apache.commons.math.analysis.solvers
> -----------------------------------------------------------------------------------------------------------
>
> Key: MATH-560
> URL: https://issues.apache.org/jira/browse/MATH-560
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Nick Fortescue
> Priority: Minor
> Fix For: 2.2.1
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> During refactoring of the solvers, an @Deprecated javadoc comment was added to the no argument constructor for a number of Solvers, saying they would be removed for 3.0.
> This is incorrect - there is no plan to remove those constructors. See the discussion on the user list on 2011-04-20. The @deprecated tag should be removed.
> This causes deprecation warnings in previously compliant code, and should not.
> This affects at least the following Solvers: MullerSolver, SecantSolver, NewtonSolver.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira