I have been reading the forums and can't find a definitive answer on this one. It seems when I do have .groovy files that are also groovy classes of the same name (like Java) I evetually
start getting a red inspector line that the class already exists. I've been careful to exclude output and target folders but still get this annoting line. I'm trying to get my team to adopt Groovy and this is not building confidence. It does not prevent compilation/building however. If the common convention is to name the class differently than the file, I'll go ahead and do that.