Issue Details (XML | Word | Printable)

Key: GROOVY-2909
Type: Sub-task Sub-task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Paul King
Reporter: Hans Dockter
Votes: 2
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
groovy
GROOVY-3087

Groovydoc does not take inheritance into consideration.

Created: 17/Jun/08 03:44 AM   Updated: 22/Jan/09 09:34 PM
Component/s: None
Affects Version/s: 1.6-beta-1
Fix Version/s: 1.6-rc-2, 1.7-beta-1

Time Tracking:
Not Specified


 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jochen Theodorou added a comment - 16/Oct/08 01:05 PM
parent task has fix version

Paul King added a comment - 04/Jan/09 06:00 AM
Can you elaborate on which aspect(s) about inheritance are key for you?

Hans Dockter added a comment - 05/Jan/09 01:34 AM
In Java, if the class GroovyCompile extends the class Compile, you get the following Javadoc snippet for GroovyCompile.
java.lang.Object
  extended by ConventionTask
      extended by org.gradle.api.tasks.compile.Compile
          extended by org.gradle.api.tasks.compile.GroovyCompile
...
public class GroovyCompile
extends Compile
...
Fields inherited from class org.gradle.api.tasks.compile.Compile
antCompile, classpathConverter, existentDirsFilter
...
Methods inherited from class org.gradle.api.tasks.compile.Compile
...

If a Groovy class extends another class, nothing of the above appears in the Groovydoc. Inherited elements do not show up.


Paul King added a comment - 05/Jan/09 07:40 AM
OK, I started adding some of this in. I have been tackling some easy items which could be done without fixing up a few underlying pieces. I am rapidly approaching the point where those pieces need to be fixed before I can go much further.