BuildSettings wasn't handling in-place plugins reliably when checking plugin dependencies. It was using new File() on the plugin location and then using the name of that File. Unfortunately, plugin test projects typically have the plugin location as "../../..", so there is no name. I've fixed it by getting the canonical file, which resolves the relative path to something that includes the actual directory name.
BuildSettings wasn't handling in-place plugins reliably when checking
plugin dependencies. It was using new File() on the plugin location and
then using the name of that File. Unfortunately, plugin test projects
typically have the plugin location as "../../..", so there is no name.
I've fixed it by getting the canonical file, which resolves the relative
path to something that includes the actual directory name.

That said, it's still fragile because it relies on the name of the
directory to determine what the name of the plugin is. For in-place
plugins, that's not guaranteed.

jeffbrown/grailsnolib,jeffbrown/grailsnolib