[
https://issues.apache.org/jira/browse/MNG-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5782.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Provide better documentation for deprecations in Maven 3
> --------------------------------------------------------
>
> Key: MNG-5782
> URL: https://issues.apache.org/jira/browse/MNG-5782
> Project: Maven
> Issue Type: Bug
> Components: Documentation: General
> Affects Versions: 3.0
> Reporter: Sergei S. Ivanov
> Priority: Major
>
> Quite a few classes and methods in Maven core API have been marked as
> deprecated as of Maven 3. Unfortunately, there is no documentation in the
> code, which suggests what the valid alternatives might be. This creates a lot
> of uncertainty for independent plugin developers, who are not privy to the
> internal design and implementation decisions made by Maven core team.
> A few examples off the top of my head:
> * the entire {{ArtifactFactory}} interface
> * all but one of {{ArtifactResolver}} interface methods
> * {{MavenProject.getCompileArtifacts()}} method
> * {{MavenProject.getTestArtifacts()}} method
> I know that some functionality is now being implemented by Aether, but using
> Aether directly is not an option if a compatibility with Maven [3.0, 3.1) is
> required.
> Can you please provide javadoc for deprecated interfaces and methods,
> explaining in greater detail the alternatives and the suggested migration
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
