-
Notifications
You must be signed in to change notification settings - Fork 356
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
Instead of throwing most MavenDownloadingException, record them into … #4140
Conversation
…the resolution result. This allows for partial success when processing poms which are invalid or contain unresolvable dependencies without hiding the existence of these problems.
@@ -66,6 +66,12 @@ public class RawPom { | |||
@Nullable | |||
String version; | |||
|
|||
// This is an obsolete field that is no longer used, but it is present in some particularly old POMs | |||
@EqualsAndHashCode.Include |
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.
Not sure it should be included in EqualsAndHashCode
} | ||
|
||
@JsonCreator | ||
ResolvedPom(Pom requested, Iterable<String> activeProfiles, Map<String, String> properties, List<ResolvedManagedDependency> dependencyManagement, @Nullable List<MavenRepository> initialRepositories, List<MavenRepository> repositories, List<Dependency> requestedDependencies, List<Plugin> plugins, List<Plugin> pluginManagement) { |
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.
This worries me. Where is the constructor going?
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.
After this PR there are no remaining invocations of the two-argument form of the constructor within OpenRewrite.
So if the two-argument constructor is gone the remaining constructor is exactly what lombok would generate, so there is no need to preserve it explicitly.
Closing this for now in favor of fixing resolution problems. Allowing a partial POM resolution will cause the downstream effect of dependency-manipulating recipes potentially not working correctly. |
…the resolution result. This allows for partial success when processing poms which are invalid or contain unresolvable dependencies without hiding the existence of these problems.
What's changed?
What's your motivation?
Anything in particular you'd like reviewers to focus on?
Anyone you would like to review specifically?
Have you considered any alternatives or workarounds?
Any additional context
Checklist