matching method is inaccessible from build.sbt

[eed3si9n]

Ref #78
matching became private[sbt], so it's no longer accessible. Prior to the change at least we could get to it via importing internal.

[dwijnand]

Ah, the use case suffering from this change is our own scripted tests..

Given the use case is so niche, how do you feel about us finding a call-site workaround, by defining a forwarder in a project/*.Scala util, rather than messing with the encoding here?

[eed3si9n]

Since there there are a bunch tests that use it, I think we should just expose it (and any other enrichment that looks safe) out since we're doing it for one method.

[dwijnand]

Without intending to sound facetious, do you have criteria (or a rule of thumb) for what you consider to be safe?

[eed3si9n]

Something that has concrete meaning and won't change as we might add fields in the future would be relatively safe, I think.