Improve Configuration's update result reporting
See original GitHub issueCurrently, Configuration’s update() method returns a boolean whether the update was successful or not. I feel there is some room for improvement here, for this method (or a relevant sibling method) to return more details about the update. Namely:
- message/reason for the update failing (if any)
- whether (or how many?) jars were actually updated, or there was nothing newer to get
- what is the current version of the business application jar (The one defined in Maven’s
<version />
In the business app I can get it bygetClass().getPackage().getImplementationVersion()
)
That way updates could be logged and various feedback could be provided based on the update wizard (i.e. a popup displaying that a new version is now running, possibly linking to a change log).
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Mastering Configuration Manager Patch Compliance Reporting
The following report should help you identify update problems within a specific collection and a group of systems and is designed to work...
Read more >View a report on customizations and configuration changes
View a report on customizations and configuration changes · Navigate to All > Reports > View / Run and locate the Customer Update...
Read more >Optimizing Remedy Smart Reporting performance
To configure restrictions for Remedy Smart Reporting query results, complete the following steps: Open the Usage Parameters panel.
Read more >Configuration Settings (Tenable.sc 5.23.x)
Configuration Settings ; Scan Results. The number of days you want Tenable.sc to retain scan results. The default value of this option is...
Read more >Global Advanced-Reports Settings - Qualtrics
Improve productivity. ... Results-Reports Breakouts · Global Results-Reports Settings; Visualizations ... Participant Import, Update, & Export Messages (EX).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m considering actually returning a report object instead of boolean for the next release. What information do your think should it contain?
Yes, because the default handler isn’t configured to pass you that info. Unless if you want you can change the injected method call to:
And then use reflection to get the context field; I’d recommend you against this approach though.
I assume you try to use the update overload that takes an
UpdateHandler
? In that case you can’t use injectable but you can still get all those info by directly reading that information from the instance itself.Injectable can be used when the handler gets loaded by the service mechanism or by listing it in the config under
<provider updateHandler=com.MyClass />
Perhaps tell me your general setup of the bootstrap so I can try to help.