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

Piotr Zygielo commented on MDEP-532:
------------------------------------

I think the below is better than "introduction to LC" and suggesting to change 
execution id.

[https://maven.apache.org/guides/mini/guide-configuring-plugins.html#using-the-executions-tag]
{quote}*Note:* Configurations inside the {{<executions>}} element used to 
differ from those that are outside {{<executions>}} in that they could not be 
used from a direct command line invocation because they were only applied when 
the lifecycle phase they were bound to was invoked. So you had to move a 
configuration section outside of the executions section to apply it globally to 
all invocations of the plugin. Since Maven 3.3.1 this is not the case anymore 
as you can specify on the command line the execution id for direct plugin goal 
invocation. Hence if you want to run the above plugin and it's specific 
execution1's configuration from the command-line, you can execute:

 
{{mvn myquery:query@execution1}}{quote}
 

> Undeclared test resources fail build despite 'ignoreNonCompile'
> ---------------------------------------------------------------
>
>                 Key: MDEP-532
>                 URL: https://issues.apache.org/jira/browse/MDEP-532
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: analyze
>    Affects Versions: 2.10
>         Environment: Windows 7 Pro 64-bit, Java OpenSDK 8, Maven 3.3.9
>            Reporter: Alexander Kriegisch
>            Assignee: Elliotte Rusty Harold
>            Priority: Minor
>              Labels: S2
>
> I have this plugin in my project's root POM:
> {code}
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-dependency-plugin</artifactId>
>   <version>2.10</version>
>   <executions>
>     <execution>
>       <id>analyze</id>
>       <goals>
>         <goal>analyze-only</goal>
>       </goals>
>       <configuration>
>         <failOnWarning>true</failOnWarning>
>         <ignoreNonCompile>true</ignoreNonCompile>
>         
> <ignoredUnusedDeclaredDependencies>*</ignoredUnusedDeclaredDependencies>
>       </configuration>
>     </execution>
>   </executions>
> </plugin>
> {code}
> Even though I want to ignore used undeclared test dependencies via 
> {{<ignoreNonCompile>true</ignoreNonCompile>}}, my build fails like this in 
> several modules:
> {code}
> [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze) @ xxx.yyy ---
> [WARNING] Used undeclared dependencies found:
> [WARNING]    
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.0:test
> [WARNING]    org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:test
> [WARNING]    
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.1.11.Final:test
> [WARNING]    
> org.jboss.arquillian.spock:arquillian-spock-core:jar:1.0.0.RC4_XXX:test
> [WARNING]    
> org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.0:test
> (...)
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze) 
> on project xxx.yyy: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze) 
> on project yyy.zzz: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze) 
> on project zzz.aaa: Dependency problems found -> [Help 1]
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:2.10:analyze-only (analyze) 
> on project aaa.bbb: Dependency problems found -> [Help 1]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to