[
https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=363287#comment-363287
]
Scott Carey commented on MCOMPILER-157:
---------------------------------------
This _seems_ to be the nexus of a lot of broken behavior related to annotation
processing tools. Any chance it would be reverted? It simply appears to be
the wrong thing to do. 'mvn clean compile' followed by 'mvn compile' breaks
in most builds that have annotation processors that generate classes, from what
appears to be this as the root cause.
Adding a project's generated-sources/annotations to _downstream_ projects
classpath is probably ok, but adding it to itself appears flawed -- that would
imply that 'compile' and 'clean compile' are not expected to have the same
input to the compile phase!.
MCOMPILER-235, MCOMPILER-236
> Maven Compiler Plugin should add to compileSourceRoots for next plugins to
> consider as source directory for generated files
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-157
> URL: https://jira.codehaus.org/browse/MCOMPILER-157
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Java 6
> Reporter: Zoran Regvart
> Assignee: John Casey
> Fix For: 3.2
>
> Attachments: failing-test-example.zip,
> maven-compiler-plugin-add-compileSourceRoots.patch,
> maven-compiler-plugin-addToSourcePathAsWell.patch, TestCase2.zip,
> test-case.zip
>
>
> Maven Compiler Plugin by relying on javac by default, on Java 6 platform
> includes annotation processors in it's processing, these in end could
> generate sources that are placed by default in
> target/generated-sources/annotations. The later should be added to
> compileSourceRoots so that next plugin in execution would consider those
> sources.
> Please, see the attached test case and consider the attached patch in the
> next release of maven-compiler-plugin.
> thanks,
> Zoran
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
