On 19.05.19 14:26, Paul King wrote:
True. But "good" separation of concerns is to some degree in the eye of the beholder. Separating by language of implementation caters for one concern, i.e. language of implementation. Another way would be to group all source related to one bit of functionality together and hide away a potentially unimportant detail being the language of implementation. We could debate this but we always try to be pragmatic and we get benefit from Gradle from the former. So, I did that for the src/main folder. I have only done this in master so far and wasn't planning to back port to 2_5_X at this stage. It also revealed a bunch of Javadoc assertion tests that weren't being run. That is fixed also.
and how did the build times change? Do we still have incremental builds for the java parts? Because as I understood Cedric this is not the case anymore now. For development I think it depends on your IDE-setup what you need. I usually have the sources compiled by the IDE for java and them being used over the Groovy jar. That way I do not to rebuild the jar for most cases. And in that kind of setup the gradle really is only needed for a full build. But that setup is actually difficult to explain to the IDEs. If you go with the more obvious version and let the IDE rebuild the jars everytime you execute, then you do want incremental builds normally. bye Jochen
