[jira] [Commented] (MCOMPILER-262) When using annotationProcessorPaths, the project dependencies must not be added as well

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

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

Hudson commented on MCOMPILER-262:
----------------------------------

SUCCESS: Integrated in maven-plugins #5036 (See [https://builds.apache.org/job/maven-plugins/5036/])
[MCOMPILER-262] Don't add project dependencies to -processorpath when using the annotationProcessorPaths option, but only the dependencies of the processor artifacts. (agudian: [http://svn.apache.org/viewvc/?view=rev&rev=1727176])
* maven-compiler-plugin/src/it/MCOMPILER-203-processorpath/annotation-processor/pom.xml
* maven-compiler-plugin/src/it/MCOMPILER-203-processorpath/annotation-processor/src/main/java/org/issue/SimpleAnnotationProcessor.java
* maven-compiler-plugin/src/it/MCOMPILER-203-processorpath/annotation-user/pom.xml
* maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java


> When using annotationProcessorPaths, the project dependencies must not be added as well
> ---------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-262
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-262
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.5
>            Reporter: Andreas Gudian
>            Assignee: Andreas Gudian
>             Fix For: 3.5.1
>
>
> In the newly introduces {{annotationProcessorPaths}} feature, I accidentally included the project's dependencies to the {{processorpath}}. That's totally not the intention.
> Only the listed artifacts and their transitive dependencies are to be included in {{processorpath}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)