[
https://issues.apache.org/jira/browse/GROOVY-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898841#comment-15898841
]
Paul King commented on GROOVY-8105:
-----------------------------------
Well, it is very useful for Java interoperability just not currently in the
context of joint compilation.
To explain a bit more with an example, suppose you are building a library that
you may want to use from Java, you can write it in Groovy and use @Builder to
provide the kind of type safe builder style api that you'd expect had the
library been written in Java.
So, happy for the documentation to be improved, but it's not a case of removing
the existing wording but it would rather be elaborating further on what
scenarios are and are not expected to currently work.
> @Builder isn't useful for java interop
> --------------------------------------
>
> Key: GROOVY-8105
> URL: https://issues.apache.org/jira/browse/GROOVY-8105
> Project: Groovy
> Issue Type: Improvement
> Components: GroovyDoc
> Reporter: Michael Martz
> Priority: Minor
>
> See https://github.com/groovy/groovy-eclipse/issues/178 for context. The
> javadoc for the @Builder AST annotation indicate that it might be good for
> Java interoperability, however it appears that this is not the case. This
> should be removed from the javadoc for this annotation.
> Specifically it says "But if you need Java integration or in some cases
> improved type safety, the @Builder transform might prove very useful."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
