maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <>
Subject [jira] [Resolved] (MCOMPILER-202) Plugin dependencies not added to compiler classpath with
Date Fri, 05 Feb 2016 18:10:40 GMT


Andreas Gudian resolved MCOMPILER-202.
    Resolution: Duplicate

> Plugin dependencies not added to compiler classpath with
> -----------------------------------------------------------------------------
>                 Key: MCOMPILER-202
>                 URL:
>             Project: Maven 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
> This seems to be due to the switch to {{}} as setting {{forceJavacCompilerUse}}
to {{true}} works around the issue.
> To reproduce:
> 1. clone
> 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 which lead me to
create this issue.

This message was sent by Atlassian JIRA

View raw message