On Mon, 4 Apr 2022 at 08:51, Tibor Digana <tibordig...@apache.org> wrote:

> Regarding the next 4 reports out of 5:
>
> Test report
> Checkstyle report
> PMD report and
> Taglist report
>
> we should use the Sonar Cube as a substitution and the development +
> release process should take the Sonar into account on the fly.
>

no need for yet another external tool as we already use Jenkins.
Jenkins already offers test report, jacoco
https://ci-maven.apache.org/job/Maven/job/ci-reporting-test/job/maven-compiler-plugin/job/ci-reporting/

And now even some static analysis data collection of data produced by Maven
plugins as prototyped here
https://ci-maven.apache.org/job/Maven/job/ci-reporting-test/job/maven-compiler-plugin/job/ci-reporting/2/linux-jdk11/


> Then I would understand the purpose of removal.
> But now I don't!
>
> T
>
>
>
>
> On Sun, Apr 3, 2022 at 10:46 PM Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> wrote:
>
> > Hi,
> >
> > We have plans for the next release for parents poms.
> >
> > Maybe I will be boring, but I still do not see any values for some of the
> > reports for static documentation sites of components.
> >
> > Result of tests during release time has no value after some time.
> Important
> > is the current result of tests on CI systems.
> >
> > Maybe someone will show me the value of it ... so I will stop asking.
> >
> > So proposition to remove:
> >
> > - surefire [1]
> > - checkstyle [2]
> > - pmd [3]
> > - taglist [4]
> > - invoker [5]
> >
> > [1] https://github.com/apache/maven-parent/pull/49
> > [2] https://github.com/apache/maven-parent/pull/51
> > [3] https://github.com/apache/maven-parent/pull/52
> > [4] https://github.com/apache/maven-parent/pull/53
> > [5] https://github.com/apache/maven-parent/pull/54
> >
> >
> > --
> > SÅ‚awomir Jaranowski
> >
>

Reply via email to