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
There are two usage modes:
auto config
with explicit configuration file
Based on this description, I imagine "auto config release" automatically come up with configurations based on the current arrangement without explicit config files.
Just my guess :)
Would be nice to have more callouts about "Auto config release", so that users would not wonder about "auto config release" task in maven and gradle.
FWIW auto-config releases only work with the release step. At the moment deploy targets will be skipped as there's no way to define all required arguments.
I found there is a
jreleaser:auto-config-release
maven task but could not find detailed documentation about what the "auto-config" means.In the JReleaser CLI page release section, it describes:
Based on this description, I imagine "auto config release" automatically come up with configurations based on the current arrangement without explicit config files.
Just my guess :)
Would be nice to have more callouts about "Auto config release", so that users would not wonder about "auto config release" task in maven and gradle.
In addition, I typed "auto config" on the search box on the documentation, and the "Auto Config Release" search result jumps to this url - https://jreleaser.org/guide/latest/examples/auto-config-release.html - which gives Page Not Found.
The text was updated successfully, but these errors were encountered: