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

Fixing ProjectReload with missing artifacts #7855

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

sdedic
Copy link
Member

@sdedic sdedic commented Oct 9, 2024

It was discovered that if ProjectReload.withProjectState is used and the project contains a truly unresolvable artifact (i.e. a reference to a local custom build, that can be never downloaded), the priming support will keep telling the project state is not good. The past priming information (with an old timestamp) was incorrectly cached and has been merged with the new MavenProject, but degraded its timestamp ... so it was older than constituent files, which resulted in an inconsistent state right after load.

This PR extends the SPI to indicate that the ReloadImplementation should execute whenever previous ReloadImplementations changed anything. It also fixes various conditions with missing artifacts and project (re)loads - see the added test cases.

@sdedic sdedic added Maven [ci] enable "build tools" tests enterprise [ci] enable enterprise job labels Oct 9, 2024
@sdedic sdedic added this to the NB24 milestone Oct 9, 2024
@sdedic sdedic requested review from mbien and dbalek October 9, 2024 09:38
@sdedic sdedic self-assigned this Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enterprise [ci] enable enterprise job Maven [ci] enable "build tools" tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant