Yes, the split of java/groovy files into src/main[java|groovy] can be considered a bit of an anti-pattern for humans, it does help gradle. Gradle supports both but performs better when split strictly according to guidelines, e.g. for build caching purposes. All of the subprojects should be structured according to gradle guidelines but I don't think we quite ever got src/main and src/test in groovy to be fully compliant. We should probably look at that again.
On Sun, May 19, 2019 at 5:35 AM Milles, Eric (TR Tech, Content & Ops) < eric.mil...@thomsonreuters.com> wrote: > I've been curious about the split made to the main sources for a while > now. https://github.com/apache/groovy/tree/master/src/main > > > Since src/main/groovy can contain both java and groovy sources, why are > there any sources in src/main/java? For me, it makes locating and > navigating cumbersome since I need to guess which folder a source is likely > to be in. And I didn't expect to find any "org.codehaus" packages in > src/main/groovy, but there are some in there. Could they be ported to Java > so that src/main/groovy only contains the groovy.* packages? Or could all > the packages in src/main/java be moved to src/main/groovy? >
