generatesSources() exhibits confusing behavior for inexact path matches

[sdp2128]

Assume that a generatesSources() clause is evaluated under the following conditions:

• All the generated sources are parseable
• All of the expected sources are parseable
• There is at least one mismatch between the URI of the expected source list and the compiled source list

If each one of the generated sources can be paired with an expected source having an equal compilation tree, then the clause succeeds

However, if at least one generated source cannot be paired with a syntactically equal expected source, then the clause will fail with the message "Did not find a source file named ..."

The error indicates that the failure was due to a mismatched path, when in fact the clause will succeed without changing any path at all.

[sdp2128]

I think I'm beginning to understand this a little more clearly.

If I'm inferring properly, generatesSources() falls back on filenames as a way of mapping expected files to generated files. That way, IF a match isn't found, then a diff can be provided.

The behavior isn't confusing so much as the message is. Something along the lines of:

"Contents of expected source X couldn't be matched with any generated file. Attempting to provide a diff failed because none of the files generated had paths similar to X.getURI().getPath()."

That way, the user understands that the fundamental problem is a content mismatch, and that they can help remedy it with a diff by reorganizing their resources.