[jira] [Closed] (MRELEASE-992) Deprecated maven flag --no-plugin-updates shows warnings in the console output

["Robert Scholte (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRELEASE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRELEASE-992.
-----------------------------------
       Resolution: Fixed
         Assignee: Robert Scholte
    Fix Version/s: 3.0.0

Fixed in [69831b60fedba2d94afd8d15a81e580acdef23e7|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=69831b60fedba2d94afd8d15a81e580acdef23e7]

> Deprecated maven flag --no-plugin-updates shows warnings in the console output
> ------------------------------------------------------------------------------
>
>                 Key: MRELEASE-992
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-992
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>    Affects Versions: 2.5.3
>            Reporter: Victor Martinez
>            Assignee: Robert Scholte
>            Priority: Minor
>              Labels: maven
>             Fix For: 3.0.0
>
>
> Hi there,
> It seems some maven flags have been deprecated since Maven 3.0 (see MNG-4697) and still used by the maven-release plugin (see [here|https://github.com/apache/maven-release/blob/4ce69b81b9230f294338a5875ca1cf9333664808/maven-release-manager/src/main/java/org/apache/maven/shared/release/exec/ForkedMavenExecutor.java#L127] which caused some warning output:
> {code}
> [WARNING] Command line option -npu is deprecated and will be removed in future Maven versions.
> {code}
> Just wondering whether it makes sense to get rid of that particular flag within the maven-release plugin or just kept as a backward compatibility feature?
> Thanks 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)