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
nddipiazza-ebay
changed the title
Default behavior should be print some basic bare bones info about recipes
Default behavior should be print some basic heartbeat mvn console
Nov 25, 2024
nddipiazza-ebay
changed the title
Default behavior should be print some basic heartbeat mvn console
Default behavior should be print some basic heartbeat in console
Nov 25, 2024
nddipiazza-ebay
changed the title
Default behavior should be print some basic heartbeat in console
Default behavior should be to print some basic heartbeat in console
Nov 25, 2024
hi @nddipiazza-ebay ; Appreciate your concern when running on a large project; We've had some internal discussions around this subject in the past as well, most recently in
In short we're hesitant to add logging to the plugins, as it's hard to provide a uniform experience there. For large projects the OSS Maven and Gradle projects aren't a perfect fit either, as you'd have to be able to keep the full model in memory and it gets discarded after every recipe run. This in contrast to the Moderne CLI which serializes the model, and can handle large projects easily. Perhaps you'd care to evaluate that for your use cases there? Happy to discuss that on a call if needed.
Also: perhaps you'd be interested to pass in -Drewrite.metricsUri=LOG or even a proper URI to get some metrics out of your recipe runs; that might help you to monitor what the run is doing.
Any time spent downloading should be visible from the debug logging already as well
When I run a open rewrite maven plugin on a big project,
Here is my default logging:
Meanwhile left wondering hmmmmm I wonder how it's going?
The Default logging some have some basic heartbeat.
The text was updated successfully, but these errors were encountered: