Details
Description
Originally reported for Camel Quarkus here:
https://github.com/apache/camel-quarkus/issues/5427
I think the implementation of poll() in the Jira WatchUpdatesConsumer is not correct.
If the number of issues found during the poll has changed compared to previous, then for some reason it invokes init(). It should probably be invoking initIssues to refresh the map of watched issues. Otherwise the consumer is only able to watch for updates on issues that were created before the route was started.