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

Differentiate between 3rd party JARs and customer owned JARs #217

Open
mnriem opened this issue Apr 17, 2024 · 3 comments
Open

Differentiate between 3rd party JARs and customer owned JARs #217

mnriem opened this issue Apr 17, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@mnriem
Copy link

mnriem commented Apr 17, 2024

We default every unknown JARs as from a third party when it could be customer's own.

@brunoborges
Copy link
Member

I think this would require a user-provided catalogue of libraries (GAV coordinates, JAR names, etc). Can you elaborate a bit more on the downside of flagging customers' libraries as "unknown JAR"?

@mnriem
Copy link
Author

mnriem commented May 20, 2024

The customer is looking for a way to differentiate between an unknown JAR and something they delivered themselves.

@dsgrieve
Copy link

Seems like they should be able to get this out of MANIFEST.MF and or META-INF/*.SF, if they are following good practices.

@brunoborges brunoborges added enhancement New feature or request and removed triage labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants