Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.5.1Release
-
Fix Version/s: 2.5.2.Release
-
Component/s: Maven integration
-
Labels:None
-
Number of attachments :
Description
When a project contains empty groovy src folders the plugin will not look for java source and just assume no source exists. This typically happens in a couple of common scenarios that follow the maven convention of split source trees:
1) groovy is only used for testing purposes thus src/main/groovy does not exist or is empty
2) multi-module projects where not all modules use groovy
This is a really annoying issue. The workaround is to include a Dummy.groovy file in every empty groovy source dir - ie you just cannot have empty source dirs
I tried with this project and cannot reproduce your problem. Does this work for you?
Can you attach a failing project for me to test?