-
-
Notifications
You must be signed in to change notification settings - Fork 561
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
apache-2.0 license detected for a lgpl license text #285
Comments
Good catch. Can you add a test in the #86 branch ? |
I added new rules too that should fix this |
@pombredanne I think the primary goal should be to delete the wrong rule...right? |
nope, the primary is to ensure things are detected correctly. The rules in the #86 branch are rather different than in develop |
The Apache rule detected is a 50% match with |
@pombredanne
|
as I said above deleting a rule is not the solution here: the problem you found is due to a bug in the code |
ok, got it 👍 |
I you want to give it a shot, you can enable tracing flags to |
This is all fixed and passing develop |
file: pom.xml.txt
when the above file is scanned for licenses using the branch #86
apache-2.0
is detected instead oflgpl-2.1
license.But when the same file is scanned with the branch
develop
anlgpl-2.0-plus
license is detected.The text was updated successfully, but these errors were encountered: