Ethan Atkins 9040e57932 Unseal Parser ... Although this is technically in the internal package, it is exposed to users when they write a custom input task. I do not think that we should prevent users/plugin authors from writing their own parser implementations if there is a different library they prefer. By my count, there are 21 implementations of this interface in sbt, so it's unlikely that there is much benefit from a pattern matching perspective.		2019-03-15 11:11:25 -07:00
..
main/scala/sbt/internal/util	Unseal Parser	2019-03-15 11:11:25 -07:00
test/scala	Update header	2018-09-14 04:53:36 -04:00