[
https://jira.codehaus.org/browse/MCOMPILER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322737#comment-322737
]
Thomas Broyer commented on MCOMPILER-202:
-----------------------------------------
I just tried with {{-Dmaven.compiler.fork}} and annotations aren't processed,
with either 2.5 or 3.0, so it looks like using plugin dependencies never was a
supported use-case.
See also https://github.com/square/dagger/issues/194 (using 3.0 with
{{forceJavacCompilerUse}} doesn't work on OSX, with Apple's JDK 6, so we'll
revert the change in Dagger to use a provided or optional project dependency)
> Plugin dependencies not added to compiler classpath with javax.tools.Compiler
> -----------------------------------------------------------------------------
>
> Key: MCOMPILER-202
> URL: https://jira.codehaus.org/browse/MCOMPILER-202
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.0
> Environment: Maven 3.0.4, Ubuntu 12.10, OpenJDK 6u27 (Ubuntu
> package), OpenJDK 7u15 (Ubuntu package), Oracle JDK 6u27, Oracle JDK 8
> (1.8.0-ea-b81)
> Reporter: Thomas Broyer
>
> Dependencies added to the maven-compiler-plugin used to be added to the
> compiler classpath with previous versions (tested with 2.4, 2.5 and 2.5.1)
> but no longer are with 3.0. This was very useful for annotation processors,
> that shouldn't affect dependency mediation in downstream projects.
> This seems to be due to the switch to {{javax.tools}} as setting
> {{forceJavacCompilerUse}} to {{true}} works around the issue.
> To reproduce:
> 1. clone https://github.com/square/dagger/
> 2. edit examples/simple/pom.xml and move the {{dagger-compiler}} dependency
> into the {{maven-compiler-plugin}}, and set the m-c-p version to 3.0
> 3. {{mvn package}}
> *Expected behavior:*
> sources should be generated into {{target/generated-sources/annotations}} and
> there should be {{xxx$InjectAdapter}} and {{xxx$ModuleAdapter}} classes in
> {{target/classes}}.
> Now change the m-c-p version to 2.5.1 or set {{forceJavacCompilerUse}} to
> {{true}}: behavior is as expected.
> Ideally, we'd want MCOMPILER-134 with an explicit {{processorpath}}.
> See also the discussion at https://github.com/square/dagger/pull/182 which
> lead me to create this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
