[jira] [Commented] (MCOMPILER-197) dependencies no more at classpath

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

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

Andreas Gudian commented on MCOMPILER-197:
------------------------------------------

I would argue that the current behaviour (not adding the plugin-deps to the compile-classpath) is the right thing to do. So I'd like to close this issue. For the use-case of annotation processors, there is now a separate configuration option.

If anyone feels different, please reopen and we can discuss it...

> dependencies no more at classpath
> ---------------------------------
>
>                 Key: MCOMPILER-197
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-197
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0
>            Reporter: Romain Manni-Bucau
>         Attachments: compiler-test.zip
>
>
> before (version 2.5.1) dependencies of compiler plugin were added to javac classpath, now it seems (didn't check so maybe it is wrong) it is no more the case
> i attached a sample. Running "mvn compile" with version 2.5.1 you'll get a file target/generated-sources/org/issue/Person_.java. With version 3.0 you get a folder target/annotations and no more file.
> This is really blocking for stuff like openjpa metamodel generation where with version 3.0 it needs to use an ant task which is not so straight forward.



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