SCTK 30.1.0 detects classpath-exception-2.0 based only on word "classpath" in Java comments

[mjherzog]

Description

Please leave a brief description of the bug or feature request:

SCTK reports a license_score=7.33 for a set of Java files based only on the word "classpath" in comments.
The match details are:
matched_rule_identifier = classpath-exception-2.0_5.RULE
matched_rule_matcher = 2-aho
matched_rule_length = 2
matched_rule_match_coverage = 2
matched-rule_relevance = 11

Since the word "classpath" is likely to appear frequently in Java comments, it would be good to avoid this false positive.

• What version of scancode-toolkit was used to generate the scan file? version 30.1.0

[pombredanne]

This make sense but https://github.com/nexB/scancode-toolkit/blob/develop/src/licensedcode/data/rules/classpath-exception-2.0_5.RULE has this text classpath exception

Would you have a file with the problematic detection to link or attach?

[pombredanne]

Never mind I can the see the issue now. For instance this C++ snippet from https://github.com/SanDisk-Open-Source/SSD_Dashboard/blob/f0240a983544a86989eec80a9a5210f2b14fa1c1/uefi/gcc/gcc-4.6.3/libjava/gnu/classpath/jdwp/natVMVirtualMachine.cc#L280:

	    using namespace gnu::classpath::jdwp::exception;
	    throw new InvalidLocationException ();

is detected by this rule and with matched_text: classpath::[jdwp]::exception; and it should not be detected if there are extra words between classpath and exception