From: Jeff A. <ja...@fa...> - 2020-05-28 19:14:25
|
On 28/05/2020 13:13, Eero Aaltonen wrote: > On Mon, May 25, 2020 at 6:43 PM Jeff Allen <ja...@fa... > <mailto:ja...@fa...>> wrote: > > Building with Gradle and accessing dependencies remotely (no JARs > checked in) were identified as prerequisites at the time. In turn, I > think building with Gradle requires re-organising the code to fit > with > its /convention over configuration/ idea > (https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:use_standard_conventions). > > At least, doing otherwise in 2.7.2 got too difficult for me, > somewhere > around exposed classes ISTR. > > > Regarding the jars, are you > * going to keep the history intact and the jars in the resulting Git > repository or > * a harsher break dropping the binaries completely? What we have (jars and all) will be on the 2.7 branch, where Gradle would not go any further than I got with jython-slim. GitHub discourages large binary files, and large repos generally, but we're not at the point where it makes us use their large file store. I've been doing a project with just Gradle (and structured according to Gradle's liking, which was my point). I foresee a 3.8 branch built the same way and not using ant or checking in dependencies at all. Jeff Allen |