[
http://jira.codehaus.org/browse/MGROOVY-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119205
]
Luke Daley commented on MGROOVY-102:
------------------------------------
This also begs the question of what to do with the groovy doc :S
// MyClass.groovy
class MyClass {
/**
* Some documentation here
*/
def var = null
}
// Generated stub ...
public class MyClass extends Object {
/**
* Some documentation here
*/
public Object getVar() { throw new Error(); }
public void setVar(Object var) { throw new Error(); }
}
I think attaching the documentation to the getter makes sense. But what if the
groovy class defines it's own getter with groovydoc comments?
> Getters/Setters should be generated for properties.
> ---------------------------------------------------
>
> Key: MGROOVY-102
> URL: http://jira.codehaus.org/browse/MGROOVY-102
> Project: Maven 2.x Groovy Integration
> Issue Type: Improvement
> Components: stub generation
> Affects Versions: 1.0-beta-3
> Reporter: Luke Daley
> Assignee: Jason Dillon
>
> Consider the following ...
> public interface ExampleInterface {
> public void setExampleProperty(Object exampleProperty);
> }
> And the following groovy class ...
> class ExampleClass implements ExampleInterface {
> def exampleProperty
> }
> This should work and does if you aren't using the joint compile stuff.
--
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
