Groovy sourceSets support

jreznot commented 6 years ago

Previously, we had problems with Gradle 4 and entities enhancing : https://youtrack.cuba-platform.com/issue/STUDIO-4632

Please check if we can use Groovy without hacks and how it works with entities enhancing.

Check if we have duplicated classes in JARs.

jreznot commented 5 years ago

groovy-support

Right now we are using deprecated Gradle properties in order to support Groovy integration

jreznot commented 5 years ago

Relates to #99

jreznot commented 5 years ago

Relates to #60

dtsaryov commented 5 years ago

It's suggested to split java & groovy source sets into different directories. This solution has the following benefits:

we'll be able to get rid of our hack to avoid class files duplicates, everything will work out-of-the-box
correct Gradle caches mechanism working
an ability to enhance classes from all available source sets
future potential to integrate with other languages

The main concern is about future projects structure. Two options are available:

just use directories with other names for different source sets (java - src, groovy - groovySrc, etc)
canonical Maven structure

cuba-platform / cuba-gradle-plugin