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

Add Support for ".pom" file parsing in Maven ecosystem #471

Open
siyadava-sindhu opened this issue Mar 10, 2023 · 0 comments · May be fixed by #544
Open

Add Support for ".pom" file parsing in Maven ecosystem #471

siyadava-sindhu opened this issue Mar 10, 2023 · 0 comments · May be fixed by #544
Labels
detector:maven The Maven detector status:requirements Full requirements are not yet known, so implementation should not be started

Comments

@siyadava-sindhu
Copy link
Contributor

More context w.r.t above request:

  • Recently we have observed that in AndroidBuildTools repo (which helps to download 3rd party packages for OMR from web and add to office-feed , so that OMR products can use them since OMR repo has offline-build) , packages defined in ‘maven’ ecosystem are not getting detected by ComponentGovernance tool, and on further debugging its observed that AndroidBuildTools repo uses “.pom” files for maven dependencies info & CG support only ‘pom.xml’ file for Maven ecosystem.
  • To ensure Repos which uses ".pom" config file for maven ecosystem, raising this new request on 'parsing .pom file' so that we'll be security-compliant in these repos too.(eg:AndroidBuildTools)
@melotic melotic added status:requirements Full requirements are not yet known, so implementation should not be started detector:maven The Maven detector labels Mar 10, 2023
@melotic melotic linked a pull request Jun 26, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
detector:maven The Maven detector status:requirements Full requirements are not yet known, so implementation should not be started
Projects
Development

Successfully merging a pull request may close this issue.

2 participants