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

Robert Scholte commented on MNG-6562:
-------------------------------------

I think we've identified 2 issues:
- warnings are shown for all modules of the multimodule project, not just the 
reactor (the active projects). 
- warnings are shown for all plugins. I would like to see this only for the 
plugins related to the called lifecycle. i.e. if I never use 'clean' or 'site', 
I don't want to see warnings about plugins bound to these lifecycles. Once I 
use them I should get that warning, and that is soon enough for me.

I agree that we need to work on a bom for pluginManagement too.

> WARN if plugins injected by default lifecycle bindings don't have their 
> version locked in pom.xml or parent
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-6562
>                 URL: https://issues.apache.org/jira/browse/MNG-6562
>             Project: Maven
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.6.0
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>            Priority: Major
>             Fix For: 3.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, when building from a basic pom.xml:
> {code:xml}<project>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>com.mycompany.app</groupId>
>   <artifactId>my-app</artifactId>
>   <version>1.0-SNAPSHOT</version>
> </project>{code}
> many plugins are used, but their version is not locked by the user: the 
> default plugins versions depend on Maven version used, which is not stable 
> over different Maven versions.
> Adding a warning for this stability issue will help users know that they need 
> to lock down plugins versions in their pom (or parent), something like:
> {noformat}[WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for com.mycompany.app:my-app:jar:1.0-SNAPSHOT
> [WARNING] Version not locked for default bindings plugins 
> [maven-install-plugin, maven-resources-plugin, maven-surefire-plugin, 
> maven-compiler-plugin, maven-jar-plugin, maven-deploy-plugin, 
> maven-site-plugin], you should define versions in pluginManagement section of 
> your pom.xml or parent
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.{noformat}



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

Reply via email to