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

Maven project cache cannot be done if one of pom.xml of the workspace doesn't define artifact id. #475

Merged
merged 1 commit into from
Jul 30, 2023

Conversation

angelozerr
Copy link
Contributor

@angelozerr angelozerr commented Jul 30, 2023

Maven project cache cannot be done if one of pom.xml of the workspace
doesn't define artifact id.

If there is one pom.xml in the workspace which doesn't define an artifactid, a version or a groupdid, the call of ArtifactUtils.key and ArtifactUtils.versionLessKey throws an exception and breaks the all code.

For instance it breaks the cache of some pom.xml if ArtifactUtils.key is called with an artifcat which have no group id.

@angelozerr angelozerr force-pushed the artifact-no-validation2 branch 3 times, most recently from 275f450 to 5bd73be Compare July 30, 2023 16:09
doesn't define artifact id.

Signed-off-by: azerr <azerr@redhat.com>
Copy link
Contributor

@vrubezhny vrubezhny left a comment

Choose a reason for hiding this comment

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

Great catch and great fix. Thank you!

@vrubezhny vrubezhny merged commit 95989dc into eclipse:master Jul 30, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants