Skip to content

Linkage Monitor not to read dependencyManagement section of parent poms#1960

Closed
suztomo wants to merge 1 commit into
masterfrom
i1958
Closed

Linkage Monitor not to read dependencyManagement section of parent poms#1960
suztomo wants to merge 1 commit into
masterfrom
i1958

Conversation

@suztomo

@suztomo suztomo commented Feb 25, 2021

Copy link
Copy Markdown
Contributor

Fixes #1958.

@elharo Do you think of a better way than checking "-bom" to distinguish a BOM from a non-BOM?

@google-cla google-cla Bot added the cla: yes label Feb 25, 2021
@suztomo suztomo requested a review from elharo February 25, 2021 23:11

@elharo elharo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would a BOM have a dependenciesManagement section and not a dependencies section?

@suztomo

suztomo commented Feb 25, 2021

Copy link
Copy Markdown
Contributor Author

@elharo (I might not get the implication of your question.) BOM has a dependencyManagement section. BOM would not have dependencies section.

The same for a parent POM (such as google-cloud-asset-parent pom.xml). A parent pom may have a dependencyManagement section and would not have dependencies section.

@elharo

elharo commented Feb 25, 2021

Copy link
Copy Markdown
Contributor

Is there a difference between a BOM and a parent POM then? Or could one theoretically be used in place of the other? That is,

  • BOMs: have a dependencyManagement section and do not have a dependencies section
  • non-BOMs: have a dependencies section. Might have a dependencyManagement section.

Thinking about it, I think the difference between a BOM and a parent pom is how they're imported, not any content in the pom.xml itself. Is that a useful way to think about this?

@suztomo

suztomo commented Feb 25, 2021 via email

Copy link
Copy Markdown
Contributor Author

@elharo

elharo commented Feb 26, 2021

Copy link
Copy Markdown
Contributor

I just saw Stephanie's issue. I'm not sure what the right fix is here. I might need to sleep on this one.

Generically what's the problem with checking a parent pom a we would a BOM? Do we think linkage errors are OK there? I suppose it's possible that the entire set of artifacts is never used together, but that's true for any BOM.

@suztomo suztomo closed this Feb 26, 2021
@suztomo

suztomo commented Feb 26, 2021

Copy link
Copy Markdown
Contributor Author

To implement it as reading a file that lists artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Linkage Monitor unexpectedly recognizes the root parent pom as a BOM

2 participants