Greg,

My 5 cents:

I do agree with you, but we lack -- as usual -- manpower.
The Doxia stack (doxia, site plugin, etc) was lagging a LOT behind
current development, and Michael did a great job to update it (but it
took him 4 years!), but many plugins are still on the 1.x stack.

Personally I find site feature overblown, overcomplicated and just too
fragile. And ultimately, way too hard to keep it up to date.
However, I do agree that Maven is a great source of metadata (usable
on websites), and reports, but my personal pet peeve is that Maven
*should not render*. IMHO, it should produce various data sources and
report sources in some intermediate format (like asciidoc or markdown
or whatever) and let users render it in any way they want (for example
by calling hugo with exec plugin). Basically Maven should be used as a
source of "reports" extracted/generated from codebase, and that mixed
with "site content" should produce the final site. I disagree with the
"site rendering is tied to release" principle either (or the opposite:
always publish a snapshot site, while users are using things for
Central that are releases).

Maven Site stack will never be able to be on par with current SSGs.

That said, to not steal this thread, Greg, you could start another
thread about this topic.

Thanks
T

On Thu, Sep 11, 2025 at 2:20 AM Greg Chabala <greg.chab...@gmail.com> wrote:
>
> Non-binding -1
>
> I don't know what the threshold for 'widely used' should be for an optional
> reporting plugin. I see 200+ results in the search provided.
>
> I'm a user of it. In general, I think Maven site generation is
> underappreciated, underutilized, and not well advertised as a feature,
> which makes the optional add-ons to site generation like link checking even
> less popular.
>
> I'd prefer to see more improvements to the default site and the site
> lifecycle in the hope of getting more folks using it.
>
> Greg Chabala

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to