[
https://issues.apache.org/jira/browse/MNG-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564551#comment-17564551
]
Robert Scholte commented on MNG-5091:
-------------------------------------
[~astubbs] that means you either need to update those groovy dependencies or
switch to
[maven-scripting-plugin|https://maven.apache.org/plugins/maven-scripting-plugin/].
Check
https://maven.apache.org/plugins/maven-scripting-plugin/configure-the-script-engine.html
how to configure it for groovy.
> Add option to fail build if WARNING's appear in POM
> ---------------------------------------------------
>
> Key: MNG-5091
> URL: https://issues.apache.org/jira/browse/MNG-5091
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, POM
> Affects Versions: 3.0.3
> Reporter: Karl Heinz Marbaise
> Priority: Minor
> Attachments: MNG-5091-maven-embedder.patch
>
>
> It would be nice to have the option to let a build fail if something like
> this will appear:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for com.soebes.training.module:050-project-without-warnings:jar:0.1.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must
> be unique: org.slf4j:slf4j-api:jar -> duplicate declaration of version 1.6.1
> @ line 28, column 14
> [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.
> [WARNING]
> {code}
> This shoud be done for WARNING's in case of missing versions for plugins etc.
> Currently it is possible to set the Validation leven in Jenkins/Hudson
> already but it is not possible on command line. So an option on command line
> like:
> {code}
> mvn --fail-warning ...
> {code}
> would be great. Or may be a good supplemental option to set the validation
> level like:
> {code}
> mvn --validation-level MINIMAL
> mvn --validation-level MAVEN20
> mvn --validation-level MAVEN30
> mvn --validation-level MAVEN31
> mvn --validation-level DEFAULT
> {code}
> or may be both. May this might be an enhancement for Maven 3.0.4 ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
