Closed jeacott1 closed 2 years ago
I'm having trouble reproducing this. I thought maybe it'd happen in a project that didn't have any groovy files in it, but that wasn't the issue. What version of Maven are you using?
You probably don't need the <testSources>
anyway. But one thing you might try if you want to have it is to also specify a directory to apply the pattern to, like
<testSources>
<testSource>
<directory>${project.basedir}/src/test/groovy</directory>
<includes>
<include>**/*.groovy</include>
</includes>
</testSource>
</testSources>
I'm not sure if that's the cause (I haven't been able to reproduce it), but might be something to try.
@keeganwitt maven 3.6.3, Java version: 1.8.0_202 thousands of groovy files, and a few java files mixed in. I haven't seen this issue before but its incredibly consistent with this project.
I've had to resort to using the maven ant plugin to build this project for the moment, which is working - the maven-eclipse groovy plugin doesn't come close. I'll try the test-sources with the dir.
What's the structure? Are all those files in src? Or in several directories? Just trying to get an idea of things to try to reproduce.
Closing issue for now, but if you can provide information on how to reproduce, I'll reopen.
Null Pointer Exception trying to build a joint project groovy 2.4.8 gmavenplus-plugin 1.12.1