michael-o commented on PR #1267: URL: https://github.com/apache/maven-site-plugin/pull/1267#issuecomment-4360328130
> > The behavior is different compared to site:run > > What do you miss exactly? This one generates everything, given a large site with quite some reports will need time, the :run does on request. Yet another issue is that Jetty is a HTTP server after all, it is much closer to the logic after deployment, especially with slash handing akin to mod_dir/mod_index. > > `site:run` gives you very detailed information on stuff it renders which is very helpful. > > What information is that exactly and isn't this also logged with this goal? Please run it yourself, you will see all info: source, report, locale, very helpful. > > I would like to align this feature with https://docs.asciidoctor.org/maven-tools/latest/plugin/goals/auto-refresh/ calling it site:auto-refresh > > I am fine with that. > > > Is the improvement not to have Jetty anymore? > > Long term yes, having a Java Servlet Container just to serve static files is way to much overhead. Compare with #1240 and feel free to comment there. There were valid complaints from user's that m-site-p is too heavyweight in terms of dependencies and I agree with that. I agree that having the weight of a Servlet Container is bad, in fact we touched this topic with @hboutemy *years* ago and wanted to move it out to a `maven-site-run-plugin`, maybe it is about time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
