[jira] Commented: (TOBAGO-204) APT does not see sources in "self" project when processing generated sources

["Bernd Bohmann (JIRA)" <de...@myfaces.apache.org>]

    [ http://issues.apache.org/jira/browse/TOBAGO-204?page=comments#action_12454461 ] 
            
Bernd Bohmann commented on TOBAGO-204:
--------------------------------------

Can you test it with a project path that contains spaces, please.

> APT does not see sources in "self" project when processing generated sources
> ----------------------------------------------------------------------------
>
>                 Key: TOBAGO-204
>                 URL: http://issues.apache.org/jira/browse/TOBAGO-204
>             Project: MyFaces Tobago
>          Issue Type: Bug
>          Components: Maven Apt Plugin
>    Affects Versions: 1.0.8
>            Reporter: Thierry Monney
>            Priority: Minor
>         Attachments: projects.zip, workingDir.patch
>
>
> We have a multi-module setup in which module A defines an annotation processor and module B uses maven-apt-plugin to generate source code. The generation itself works OK.
> When APT runs on the generated sources, since the working directory is ${tempRoot} in forked mode, APT has no access to source files. This looks like normal behavior from APT point of view (the same happens on the command line), but results in parsing errors (although the generated code is correct and builds correctly).
> A solution would be to add a ${workingDir} parameter to the mojo and make it point to the project source folder. I will submit a patch shortly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira