slawekjaranowski commented on PR #51:
URL: https://github.com/apache/maven-parent/pull/51#issuecomment-1093795228
My opinion is the same as @olamy ... we don't need store such information
corresponding for release build time.
Nowadays we have ci system for it.
And when checkstyle fin
slawekjaranowski commented on PR #51:
URL: https://github.com/apache/maven-parent/pull/51#issuecomment-1086956261
https://maven.apache.org/plugins/maven-clean-plugin/checkstyle.html
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
slawekjaranowski commented on pull request #51:
URL: https://github.com/apache/maven-parent/pull/51#issuecomment-1052127024
@olamy are working on such reports during build time on jenkins.
Having report here we have view on issues in release time, more of component
is release not oft
slawekjaranowski commented on pull request #51:
URL: https://github.com/apache/maven-parent/pull/51#issuecomment-1051128816
I will not fight for it
--
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 t
slawekjaranowski commented on pull request #51:
URL: https://github.com/apache/maven-parent/pull/51#issuecomment-1051120681
We heave many other important issues that work with accepted rules ...
--
This is an automated message from the Apache Git Service.
To respond to the message, pl
slawekjaranowski commented on pull request #51:
URL: https://github.com/apache/maven-parent/pull/51#issuecomment-1051106585
Check style is used during each build and all discovered violations break
build.
I don't see valuable usage for skipped rules report.
--
This is an automated me
