On Fri, 25 Feb 2022 at 06:53, Tamás Cservenák <ta...@cservenak.net> wrote:
> Or, to rephrase; being a release mgr is not just about "a person doing $ > mvn release:prepare release:perform and pressing ENTER". > As if it is really just that, we would automate it, right? > why not? :) > > T > > On Thu, Feb 24, 2022 at 9:47 PM Tamás Cservenák <ta...@cservenak.net> > wrote: > > > Building everything for each commit is insane. > > > > Also, I find a release mgr that does NOT check is site building > beforehand > > release as sloppy. > > > > Hence, building everything on each commit just to suit sloppy release > mgrs > > is insane IMHO. > > > > My 5 cents. > > > > T > > > > On Thu, Feb 24, 2022 at 9:30 PM Olivier Lamy <ol...@apache.org> wrote: > > > >> Sounds good. > >> But who has never released something and having javadoc failing in the > >> middle of the release or the site generation failing once tag done and > >> artifacts staged… I find this a pain 😀 > >> > >> Maybe only testing javadoc works at least ? > >> > >> Btw I agree some reports could be removed > >> > >> On Fri, 25 Feb 2022 at 6:24 am, <herve.bout...@free.fr> wrote: > >> > >> > and reporting profile was done for this: > >> > - without reporting profile, just light site generation > >> > - with reporting profile, full documentation site > >> > > >> > disabling reporting profile for CI should do the job > >> > > >> > ----- Mail original ----- > >> > De: "herve boutemy" <herve.bout...@free.fr> > >> > À: "Maven Developers List" <dev@maven.apache.org> > >> > Envoyé: Jeudi 24 Février 2022 21:21:45 > >> > Objet: Re: Review of used reports for Maven project sites. > >> > > >> > done on GH and Jenkins, then on each commit? > >> > we're heating oceans for nothing > >> > > >> > IMHO, we need to differentiate CI vs release documentation: CI should > be > >> > much lighter than release > >> > > >> > ----- Mail original ----- > >> > De: "Slawomir Jaranowski" <s.jaranow...@gmail.com> > >> > À: "Maven Developers List" <dev@maven.apache.org> > >> > Envoyé: Jeudi 24 Février 2022 20:53:49 > >> > Objet: Re: Review of used reports for Maven project sites. > >> > > >> > Yes is done after release but also on jenkins for plugins and on GH > >> builds > >> > > >> > czw., 24 lut 2022 o 20:43 <herve.bout...@free.fr> napisał(a): > >> > > >> > > full site building with reports enabled (through reporting profile) > is > >> > > just done after release, isn't it? > >> > > > >> > > ----- Mail original ----- > >> > > De: "Slawomir Jaranowski" <s.jaranow...@gmail.com> > >> > > À: "Maven Developers List" <dev@maven.apache.org> > >> > > Envoyé: Jeudi 24 Février 2022 20:24:56 > >> > > Objet: Review of used reports for Maven project sites. > >> > > > >> > > 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 > >> > > > >> > > > --------------------------------------------------------------------- > >> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> > > For additional commands, e-mail: dev-h...@maven.apache.org > >> > > > >> > > > >> > > >> > -- > >> > Sławomir Jaranowski > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: dev-h...@maven.apache.org > >> > > >> > > >> > > >
