You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2020/05/09 16:07:00 UTC
[jira] [Commented] (MNG-6883) MavenProject - replacement for
deprecated method
[ https://issues.apache.org/jira/browse/MNG-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103352#comment-17103352 ]
Sylwester Lachiewicz commented on MNG-6883:
-------------------------------------------
Challenge for all deprecations is that it will be visible only for maven core developers. Other people will not even see new methods because all plugins import just maven 3.0 API.
But I agree - it's worth documenting what replacement we should use.
> MavenProject - replacement for deprecated method
> ------------------------------------------------
>
> Key: MNG-6883
> URL: https://issues.apache.org/jira/browse/MNG-6883
> Project: Maven
> Issue Type: Improvement
> Components: Design, Patterns & Best Practices, Documentation: General
> Affects Versions: 3.5.0
> Reporter: Slawomir Jaranowski
> Priority: Major
>
> The class {{org.apache.maven.project.MavenProject}} has many deprecated methods. There is no information what is the replacement for deprecated methods.
> Maybe some of them will be delete and others should be replaced by something else. I think that this knowledge will help to maintain custom plugins in future for developers.
> eg. I need the method
> {{org.apache.maven.project.MavenProject#getReportArtifacts}}
> and now it is deprecated ...
> I found that the change which deprecated some methods is connected to MNG-5661.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)