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

["jieryn (JIRA)" <ji...@codehaus.org>]

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

jieryn commented on MCOMPILER-197:
----------------------------------

Yep, I confirm the example project creates metamodel classes with m-compiler-p 2.5.1 for both apache maven 3.0.4 and 3.1.0. Also I confirm the example project doesn't create metamodel classes with m-compiler-p 3.0, with or without fork=true, for both mvn 3.0.4 and 3.1.0.


                
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira