jvican a36d8401e1 Don't use runtime universe to discover autoImport ... The previous implementation was using the Scala runtime universe to check whether a plugin had or not an `autoImport` member. This is a bad idea for the following reasons: * The first time you use it, you class load the whole Scalac compiler universe. Not efficient. Measurements say this is about a second. * There is a small overhead of going through the reflection API. There exists a better approach that consists in checking if `autoImport` exists with pure Java reflection. Since the class is already class loaded, we check for: * A class file named after the plugin FQN that includes `autoImport$` at the end, which means that an object named `autoImport` exists. * A field in the plugin class that is named `autoImport`. This complies with the plugin sbt specification: http://www.scala-sbt.org/1.0/docs/Plugins.html#Controlling+the+import+with+autoImport		2017-04-18 20:30:04 +02:00
..
src	Don't use runtime universe to discover autoImport	2017-04-18 20:30:04 +02:00
NOTICE	fix component name in main notice	2010-09-21 22:00:11 -04:00