You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2022/11/04 13:37:00 UTC
[jira] [Updated] (GROOVY-10162) GroovyDoc generates CLASS_NAME.1.html if an enum class has an abstract method
[ https://issues.apache.org/jira/browse/GROOVY-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Milles updated GROOVY-10162:
---------------------------------
Labels: enum (was: )
> GroovyDoc generates CLASS_NAME.1.html if an enum class has an abstract method
> -----------------------------------------------------------------------------
>
> Key: GROOVY-10162
> URL: https://issues.apache.org/jira/browse/GROOVY-10162
> Project: Groovy
> Issue Type: Bug
> Components: GroovyDoc
> Affects Versions: 3.0.8
> Environment: Ubuntu 20.04.2, Adoptopenjdk 11.0.11+9 x64
> Reporter: Kengo TODA
> Priority: Major
> Labels: enum
> Attachments: groovydoc build by Groovy 3.0.8.zip
>
>
> I found that the GroovyDoc generates `CLASS_NAME.1.html` if an enum class has an abstract method. I found this in the [spotbugs-gradle-plugin project|https://github.com/spotbugs/spotbugs-gradle-plugin/blob/3351d2b8626fa33ca6469126db1d0c220ffac9a6/src/main/groovy/com/github/spotbugs/snom/Confidence.groovy], and I've created a [MCVE project at GitHub|https://github.com/KengoTODA/unexpected-groovydoc-reproduction/tree/8b24a69f3950473bdc9f08ff930a7fccb17eefea]. The code to reproduce will be like below:
> {code:groovy}
> enum TestWithAbstractMethod {
> FOO {
> int method() { return 0; }
> },
> BAR {
> int method() { return 1; }
> }
> abstract int method();
> }
> {code}
> You can find generated HTML files in [this GitHub Actions Workflow Run|https://github.com/KengoTODA/unexpected-groovydoc-reproduction/actions/runs/1013816748]. It includes not TestWithAbstractMethod.html but TestWithAbstractMethod*.1*.html.
> The [build log contains no meaningful warning|https://github.com/KengoTODA/unexpected-groovydoc-reproduction/runs/3025284625?check_suite_focus=true#step:5:23]. I've confirmed that GroovyDoc 3.0.2 also reproduces this issue, so I guess that the change between v2 and v3 introduce this unexpected behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)