Hi Zsolt, There are a few tests in there, most are in the qa directory in the main svn repository. I think it would be great if we could find a way to merge them into the modules and follow conventions.
As far as the gradle version, did gradlew not work for you? Regards Dennis > On Jul 11, 2020, at 3:48 AM, Zsolt Kúti <la.ti...@gmail.com> wrote: > > Hi Dennis, > > Checked this out and gave it a try. Had to tell my gradle via my IDE(A) > config to use JDK 8 ( I used Adopt) and then it compiled fine. > Apart from a few warnings everything went smoothly. Out of curiosity run > tests and have seen none. Are they held separately? > Beyond that I did nothing else. Is there anything I could try? > > Zsolt > >> On Fri, Jul 10, 2020 at 9:50 PM Dennis Reedy <dennis.re...@gmail.com> wrote: >> >> Curious as to whether anyone has looked at this. >> >> Regards >> >> Dennis >> >> On Tue, Jul 7, 2020 at 1:30 PM Dennis Reedy <dennis.re...@gmail.com> >> wrote: >> >>> To demonstrate how a modular Gradle build would look like, I put together >>> a clone of Apache River subversion branch of >>> http://svn.apache.org/repos/asf/river/jtsk/modules, created as a Git >>> repository, and built with Gradle here: >>> https://github.com/dreedyman/apache-river. >>> >>> This is not to take away from the Maven effort by any means, that work >> was >>> the baseline for creating this effort last night. This is by means >>> complete, or an accepted way of building Apache River, but used as a >> means >>> to demonstrate how a modular version of Apache River can be built with >>> Gradle. >>> >>> - Besides using Gradle, there are differences in this project's >>> structure. The river-jeri, river-jrmp, river-iiop and >> river-pref-loader >>> modules have been merged into river-platform to avoid circular >> dependencies. >>> - The groovy-config module has also been enabled. >>> - All OSGi configurations have not been enabled. >>> - There were issues with the Velocity work, it was removed >>> >>> Regards >>> >>> Dennis Reedy >>> >>
