All documentation descriptions are empty

[uhafner]

I'm not sure since when this is broken: all descriptions on https://spotbugs.github.io/spotbugs-maven-plugin/plugin-info.html and all goals like https://spotbugs.github.io/spotbugs-maven-plugin/check-mojo.html are broken right now. I'm almost sure that there where descriptions in the past.

[hazendaz]

That has always been the case. Project is groovy so it uses groovydocs. See original plugin for same https://gleclaire.github.io/findbugs-maven-plugin/check-mojo.html. I believe either this was reported before or I saw it and have not figured out how to make it work.

[pzygielo]

Currently https://spotbugs.github.io/spotbugs-maven-plugin/plugin-info.html is empty

[hazendaz]

probably same reason as the other issue. project is all groovy. maven sort of expects java. Its always been this way as far as I know. If someone knows how to tie together or can help on the doxia 2 branch for site4 I have sitting on the project that would help. Maven won't fix anything from doxia 1. I don't understand doxia enough to know how to fully resolve although my site4 branch is getting closer.

[pzygielo]

probably same reason as the other issue.

It was fine for 4.8.5.0: https://web.archive.org/web/20240521073758/https://spotbugs.github.io/spotbugs-maven-plugin/plugin-info.html, but broke with:

• Update pluginPluginVersion to v3.15.0 #869

[hazendaz]

Issue was found and fixed. Doxia 2 plugins were in effect and the GHA used to push the site was not failling when encountered but could be seen locally. Thanks to @elharo pointing out that mvn site:site off master was failing. I have confirmed the site is back how it should be. If you see another other issues, please open a new ticket and thanks for the original report.

[uhafner]

Well, the original issue (before it was hijacked by @pzygielo) still is not fixed: All descriptions are still empty. Or is the fix not yet published?

[pzygielo]

I'm not sure since when this is broken: all descriptions on https://spotbugs.github.io/spotbugs-maven-plugin/plugin-info.html

That has always been the case. Project is groovy so it uses groovydocs.

and MPLUGIN-426, MPLUGIN-247.

[uhafner]

Then the issue should not be closed as completed. It should be rather closed as wont-fix or something similar.

Would it be helpful to convert this project to Java? It does not make much sense to use a language that is not fully supported by the tooling. With Copilot or ChatGPT it shouldn't be too hard. Maybe this is a good thesis topic for one of my students...

[hazendaz]

The site was fixed by me yesterday. The parent pom I also maintain is on doxia 2. This plugin is not yet on doxia 2. It broke most of the site. That is all fixed now. Issue may have been highjack, don't recall by my initial assessment was incorrect. If something is still a miss let's open a new ticket on the remaining issues. As to making java, I'll pass on that at this point. Originally when I took this over around 2016 I would have said do it. But I use groovy everyday now for jenkins and far better understand it now so I'd rather it remains groovy. Javadocs if you will are present under groovy docs. If anything if javadoc pages are an issue I'll just remove them from the site as this is pure groovy not java so there are no javadocs just groovy docs but let's start new issue as this one got mixed along the way. Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Ullrich Hafner ***@***.***> Sent: Tuesday, December 3, 2024 4:27:44 AM To: spotbugs/spotbugs-maven-plugin ***@***.***> Cc: Jeremy Landis ***@***.***>; State change ***@***.***> Subject: Re: [spotbugs/spotbugs-maven-plugin] All documentation descriptions are empty (Issue #805) Then the issue should not be closed as completed. It should be rather closed as wont-fix or something similar. Would it be helpful to convert this project to Java? It does not make much sense to use a language that is not fully supported by the tooling. With Copilot or ChatGPT it shouldn't be too hard. Maybe this is a good thesis topic for one of my students... — Reply to this email directly, view it on GitHub<#805 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHODI4YT7UDEABGWJY7QWT2DV2RBAVCNFSM6AAAAABHK4K2I2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJTHE4DCOJWGI>. You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[hazendaz]

I see original issue, reopened.

[JuditKnoll]

The original issue is duplicate of #37. However, here seems to be a bit more info.