You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nicholas Williams (JIRA)" <ji...@codehaus.org> on 2013/06/09 17:19:03 UTC

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

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

Nicholas Williams commented on MCOMPILER-197:
---------------------------------------------

Was a separate bug filed as suggested in February? This is still marked as open, so I assume not. I'm having the same issue with an annotation processor and the compiler plugin. I know there's a workaround ({{forceJavacCompilerUse}}), but I'd love to see this fixed. :-)
                
> dependencies no more at classpath
> ---------------------------------
>
>                 Key: MCOMPILER-197
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-197
>             Project: Maven 2.x 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 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