[
https://issues.apache.org/jira/browse/MCOMPILER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069727#comment-15069727
]
Andreas Gudian commented on MCOMPILER-256:
------------------------------------------
Ah, so this is the error message that you get?
{code}
[ERROR]
/home/rmannibu/dev/github/lombokmapstruct/src/main/java/test/SimpleMapper.java:[10,5]
Unknown property "value" in return type.
[INFO] 1 error
{code}
In that case, it's not because the annotation processor name was not correctly
passed to javac. If a specified processor can't be found, eg. if you pass any
garbage or a non-existing classname, the compiler will fail with a message like
{{unknown processor 'x.y.z$garbage'}} (when passing
{{<annotationProcessor>x.y.z$garbage</annotationProcessor>}}). So that's fine,
I think.
What you see then wouldn't be a problem in the Maven compiler plugin then, but
an issue with the way Lombok works - as described in
https://github.com/mapstruct/mapstruct/issues/510. Putting the processors in
order just isn't sufficient to make sure the later processors see changes made
to existing types by previous processors in the same round.
So I'll close this issue now. Please let me know if you see the "unknown
processor ..." message or think it's still related to how the processor names
are passed to javac, so that we can reopen it.
Thanks!
> annotation processors not escaped
> ---------------------------------
>
> Key: MCOMPILER-256
> URL: https://issues.apache.org/jira/browse/MCOMPILER-256
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.3
> Reporter: Romain Manni-Bucau
> Assignee: Andreas Gudian
>
> annotation processors name can contain interpreted characters in the command
> line, it should be quoted
> (http://grepcode.com/file/repo1.maven.org/maven2/org.codehaus.plexus/plexus-compiler-javac/2.5/org/codehaus/plexus/compiler/javac/JavacCompiler.java#255)
> Sample: lombok processor is an inner class so 'foo$bar' name so under UNIx it
> is broken.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
