Output formats are forced to be json,xml #3
Comments
tonybaines
added a commit
to tonybaines/gradle-use-latest-versions-plugin
that referenced
this issue
May 29, 2018
…le-versions-plugin output
|
Thanks for the quick release, working for us now. |
fibbers
added a commit
to fibbers/gradle-use-latest-versions-plugin
that referenced
this issue
Feb 7, 2019
This fixes issue patrikerdes#16. The gradle-versions-plugin has a default outputFormatter of 'plain' when not configured. You can override this by setting the task property `outputFormatter` in your build.gradle: https://github.com/ben-manes/gradle-versions-plugin#report-format Before this change, it wasn't possible to create a custom report format. By removing the hardcoded System-property `outputFormatter`, it becomes configurable again and creating custom reports is possible again. The last commit 45e15dc fixed issue patrikerdes#3, but the current version of gradle-versions-plugin should produce a plaintext report by default (also fixing the issue), so removing this System-property shouldn't introduce regression.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our nightly build takes the plain report format from gradle-versions-plugin and includes it in the notification e-mail (we don't automatically switch to the newer versions as part of CI).
After including user-latest-versions, the build fails since
build/dependencyUpdates/report.txtcan't be found.Trying to set the report formats to include 'plain' by other means fails (in the build script, via system property).
The text was updated successfully, but these errors were encountered: