You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regular build logs should indicate only important issues
Describe the solution you'd like
By default, rewriteRun should be silent in case it makes no modifications.
Currently rewrite-gradle-plugin produces
> Task :benchmarks:rewriteRun
Validating active recipes
Scanning sources in project :benchmarks
Using active styles [io.github.pgjdbc.style.Style, org.openrewrite.java.Checkstyle]
All sources parsed, running active recipes: org.openrewrite.java.OrderImports, org.openrewrite.staticanalysis.MissingOverrideAnnotation
> Task :pgjdbc-osgi-test:rewriteRun
Validating active recipes
Scanning sources in project :pgjdbc-osgi-test
Using active styles [io.github.pgjdbc.style.Style, org.openrewrite.java.Checkstyle]
All sources parsed, running active recipes: org.openrewrite.java.OrderImports, org.openrewrite.staticanalysis.MissingOverrideAnnotation
> Task :postgresql:rewriteRun
Validating active recipes
Scanning sources in project :postgresql
Using active styles [io.github.pgjdbc.style.Style, org.openrewrite.java.Checkstyle]
I believe the messages do not belong to lifecycle level. They should probably be moved to info, so they should be visible only in case the user provides --info.
Validating active, Scanning sources, and All sources parsed, running active recipes probably belong to debug level.
Have you considered any alternatives or workarounds?
What problem are you trying to solve?
Regular build logs should indicate only important issues
Describe the solution you'd like
By default,
rewriteRun
should be silent in case it makes no modifications.Currently
rewrite-gradle-plugin
producesI believe the messages do not belong to
lifecycle
level. They should probably be moved toinfo
, so they should be visible only in case the user provides--info
.Validating active
,Scanning sources
, andAll sources parsed, running active recipes
probably belong todebug
level.Have you considered any alternatives or workarounds?
Frankly speaking, no.
Additional context
I'm adding OpenRewrite to pgjdbc/pgjdbc.
Are you interested in contributing this feature to OpenRewrite?
Maybe.
The text was updated successfully, but these errors were encountered: