There is such a situation where the contributor changes the site, we vote for his PR on GH but we lately find out that the site is broken in some way. If I could see the site deployed to gh_pages which is a Git branch and visualized on GH then the contributor would fix it much better.
Of course building the site with all the combinations of Maven & JDK would be an overhead. One run is enough. T On Thu, Feb 24, 2022 at 8:25 PM Slawomir Jaranowski <s.jaranow...@gmail.com> wrote: > Hi, > > Building the Maven site takes a long time for our projects. > > Before releasing the next version of maven-parent, I have a proposal to > review used Maven site reports. > > So > > - without reporting profile, standard maven-project-info-reports-plugin - > build very quick - no problems > > - with reporting profile: > - surefire - require test phase - can have influence on build time > - checkstyle > - pmd > - jxr - needed by other reports > - taglist > - javadoc - require generate-sources > > - for plugins and extensions additional invoker report is added. > > I starting to think what of benefit we have, who is looking at reports > like: surefire, checkstyle, pmd, taglist > Maybe they are redundant - tests, checkstyle verification simply must pass > > -- > Sławomir Jaranowski >
