Allow identifying snippets on code location granularity

[fviernau]

Problem

• The identification is done via an include rules which only allows for specifying purl and path, see [1]
• Given a file which contains two snippets at different line ranges, but only one of them is valid.
• It is impossible to only mark the valid one as identified, because line range cannot be specified.
• Consequence: The process gets stuck, because there is no way to address the issue.

Proposal

Allow specifying the line range for include rules.

[1]

scanoss.java/src/main/java/com/scanoss/settings/Rule.java

Lines 33 to 37 in 13a33cb

	* Rules support two types of matching:
	* - Full match: Both path and PURL match
	* - Partial match: Either path or PURL matches
	* </p>
	*/

[tatysanic-maker22]

Hi,

After reviewing this internally, adding line-range support to the include rules isn't something we're planning to implement at this time.

For the use case you've described, we'd recommend using:

--strip-snippet, -N STRIP_SNIPPET
Strip Snippet ID string from WFP

This lets you strip the snippet ID string from the WFP, which should help you address the snippet you don't want carried through, without needing line-range granularity in the include rules.

We'll close this for now, feel free to reopen if this doesn't cover your case.

Regards,
Tatiana Coccia
Head of Customer Support
SCANOSS