Your issue may already be reported! Please search on Github issues before creating one.
-
I'm submitting a ...
-
What is the current behavior?
AMF jar are flagged as license risk. Although github repo has a page that contains license information. But, since the jar doesnot contain this information, these libraries are getting highlighted as unknown license risk.
-
If the current behavior is a bug, please provide the minimal steps to reproduce with AMF code. Please don't upload AMF code mixed with yours.
-
What is the expected behavior?
Libraries should not be flagged as license risk
-
What is the motivation/use case for changing the behavior? (for feature requests)
Jar should have the license related file inside it, which tools like blackduck can autoread.
-
Please tell us about your environment:
- AMF Version: 5.7.1
- AMF Distribution: JVM
- Operating System: linux
- Link to your project:
-
Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, Gitter, etc)
Your issue may already be reported! Please search on Github issues before creating one.
I'm submitting a ...
What is the current behavior?
AMF jar are flagged as license risk. Although github repo has a page that contains license information. But, since the jar doesnot contain this information, these libraries are getting highlighted as unknown license risk.
If the current behavior is a bug, please provide the minimal steps to reproduce with AMF code. Please don't upload AMF code mixed with yours.
What is the expected behavior?
Libraries should not be flagged as license risk
What is the motivation/use case for changing the behavior? (for feature requests)
Jar should have the license related file inside it, which tools like blackduck can autoread.
Please tell us about your environment:
Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, Gitter, etc)