HI Dennis,
Had a quick look just now, I can see why gradle is attractive.
I'm not a big fan of the larger modules, but you have demonstrated it
can work.
I guess it's a trade off between maintainability and avoiding the need
to untangle the circular links.
Have you had a look at the code changes I made to remove the circular links?
Cheers,
Peter.
On 7/11/2020 5:50 AM, Dennis Reedy 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
