Ethan Atkins 7dbf7978e9 Disable multiple main class warning w/ qualified key ... If the user runs foo/runMain in a project with multiple main classes, sbt will still warn the user about their being multiple main classes even though this is a pointless warning since the user either is running runMain which requires a main class. The run task is also excluded since by default it prompts the user with a main class selector. The previous logic for doing this filtering was bad because it only looked at the first command in a sequence and couldn't handle the foo/runMain case since it was looking for an exact match with `run` or `runMain`. This commit relaxes those restrictions to look at all of the strings in the command as well as splitting the string to check if the last part of the key ends in run or runMain. This logic could theoretically be incorrect if the user wrote an input task that was expecting run or runMain as user input but even in that case the only consequence would be that they wouldn't see the multiple main class warning which generally isn't all the helpful unless you are packaging a jar that expects there to be only one main class. It seems unlikely that that the user would be running a custom input task that is both packaging a jar and expecting run or runMain as input strings.		2021-05-30 14:48:05 -07:00
..
src	Disable multiple main class warning w/ qualified key	2021-05-30 14:48:05 -07:00
NOTICE	Add, configure & enforce file headers	2017-10-05 09:03:40 +01:00