[
http://jira.codehaus.org/browse/MGROOVY-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139963#action_139963
]
Bart Robeyns commented on MGROOVY-151:
--------------------------------------
I think there are two problems at the moment:
a: putting a script in your source-tree fails the build
b: Scripts might contain multiple classes; while it is probably not very
interesting to call the generated script-class from java-code, it might be
handy to call the contained classes.
Anyway, I think simply ignoring scripts in the stub-generator (thus solving a
and ignoring b) would be easy to implement and solves a rather hard to track
issue (I've spent some time figuring out what was wrong).
If a warning along the lines of 'script X skipped for stub-generation' is
displayed, any users trying to access script-contained classes can know what's
wrong and can easily alter their implementation (just move the class out of the
script-file).
> StubGenerator fails on groovy-script
> ------------------------------------
>
> Key: MGROOVY-151
> URL: http://jira.codehaus.org/browse/MGROOVY-151
> Project: GMaven
> Issue Type: Bug
> Components: stub generation
> Reporter: Bart Robeyns
> Assignee: Jason Dillon
> Priority: Minor
> Fix For: 1.0-rc-3
>
> Attachments: jointissue.zip
>
>
> Groovy files that contain code outside of a class definition result in
> grammar-errors. Errors that I've witnessed include
> Unknown AST: VARIABLE_DEF
> Unknown AST: EXPR
> Unknown AST: ASSERT
> The attached file contains a minimalistic maven project that reproduces the
> error when running
> mvn compile
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
