-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Drop legacy duplicated code #11501
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
base: maven-3.9.x
Are you sure you want to change the base?
Drop legacy duplicated code #11501
Conversation
Right now Maven 4 (same as 3) contains duplicated code to read update status, and due this in-JVM but also process wide synchronization is needed. For start, drop Maven legacy code and use resolver component to perform reads.
|
cherry pick from: |
|
Looks good, will pass once Resolver 1.9.25 is out. |
| /** | ||
| * DefaultUpdateCheckManager | ||
| */ | ||
| @Component(role = UpdateCheckManager.class) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unsure would I migrate this from plx to sisu; moreover, undoing this change will make other UT changes unneeded (index scanning)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I afraid that I need add scaning to UT as implementation of TrackingFileManager is sisiu
| private static final String ERROR_KEY_SUFFIX = ".error"; | ||
|
|
||
| public DefaultUpdateCheckManager() {} | ||
| @Inject |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just make/leave this plain old plx component with field injection instead, and as said above, it will leave things less intrusive re UTs
Right now Maven 4 (same as 3) contains duplicated code to read update status, and due this in-JVM but also process wide synchronization is needed.
For start, drop Maven legacy code and use resolver component to perform reads.
Following this checklist to help us incorporate your
contribution quickly and easily:
Note that commits might be squashed by a maintainer on merge.
This may not always be possible but is a best-practice.
mvn verifyto make sure basic checks pass.A more thorough check will be performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.