Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce Scanner.ChangeSetListener #12769

Open
wants to merge 1 commit into
base: jetty-12.1.x
Choose a base branch
from

Conversation

joakime
Copy link
Contributor

@joakime joakime commented Feb 5, 2025

  • Update testing for all Listeners

This is a small subset of the changes from PR #12583 made as a new PR just so we can track these changes separately from the deploy changes.

+ Update testing for all Listeners
@joakime joakime requested review from gregw and janbartel February 5, 2025 17:52
@joakime joakime self-assigned this Feb 5, 2025
Copy link
Contributor

@sbordet sbordet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a chance to cleanup this class, in particular by consolidating the "warn" logs.
They should be INFO or DEBUG level, not WARN, since we just log and ignore the failure, and the Scanner continues to operate as nothing happened.
Furthermore, remove the Scanner.warn() method, since in the rest of the class LOG.warn() is used instead.
I would prefer to see LOG.info()/debug() everywhere.

interface Listener should extend java.util.EventListener.

//Call the BulkListeners

// Call the ChangeSetListeners
reportChangeSet(changes);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would report the changes before the DiscreteListeners.
Is there a reason the changes are notified in between what was notified before?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 👀 In review
Development

Successfully merging this pull request may close these issues.

2 participants