[GROOVY-3737] groovydoc and other groovy bugs

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.6.8, 1.7.1, 1.8-beta-1
• Component/s: GroovyDoc

Environment

OS: 64 bit Vista.
Groovy Version: 1.6.4 JVM: 1.6.0_16
Eclipse 3.5 (Galilao) with plugins:
                 Groovy-Eclipse Feature 2.0.0.xx-20090910-1700-e35 org.codehaus.groovy.eclipse.feature.feature.group
                 Groovy-Eclipse JDT Patch Sources Feature 2.0.0.xx-20090910-1700-e35 org.codehaus.groovy.jdt.patch.source.feature.group
                 Groovy-Eclipse Sources Feature 2.0.0.xx-20090910-1700-e35
                                org.codehaus.groovy.eclipse.feature.source.feature.group

• Assignee: Paul King
• Reporter: Steve Buroff
• Created: 13/Sep/09 10:45
• Updated: 07/Apr/15 19:13
• Resolved: 16/Feb/10 02:21

Description

1. groovydoc doesn't understand

{@code xxx}

.
2. groovydoc doesn't handle

{@link xxx}

correctly.
If I'm in a.b.C and I write

{@link D}

it should work but it doesn't.
I must write

{@link a.b.D}

(note: same package).
3. groovydoc doesn't handle # correctly. If I write

{@link a.b.C#f()}

it displays "C#f" instead of "C.f()".
If I write

{@link a.b.C#f() C.f()}

, it displays the same thing as
before. Apparently it ignores the second argument.
4. There is no way to specify a style sheet (CSS file). This is a
significant problem for me and maybe others.
5. "<ctrl>2 r" doesn't work correctly For example if I have a method and I change its argument name, only the argument name is changed. The name in the body of the method and in the mathod's javadoc comment are not changed.
6. <alt><shift>R doesn't work correctly. For the same experiment as in 5, it changes the body but not the comment. If I try
<alt<shift>R on a field it bombs with "Unhandled event loop exception java.lang.StackOverflowError". This is a high priority since it blows away eclipse.
7. "Run as groovy shell" doesn't work. The shell starts and prints its startup message to the console. It then apparently exits immediately with no error message.
8. If a class file has a comment (even an empty one) before the package declaration, then it doesn't display the comment before the "class xxx" line as it should. I don't think javadoc does this. In fact I think javadoc uses a file named
package-doc.java with the comment before the package declaration to generate the package.html file.