Phil,
If nothing else comes of this, I want to thank you for the phrase "FSM help
me”. I had to look it up, and had a huge grin reading the wikipedia page I
found. Wow!
Any way, I think Peter’s work includes much of the conversion to a build using
maven modules. I am not maven averse, but neither am I gradle negative. My
enthusiasm for the maven build is based on a hope it would lead to clearer
delineation of components (some of which share the same source code, but
produce separate jars with some of the same class files as needed). I’d be
happy to lend a hand with any maven issue that pops up, but would not lambast a
gradle approach.
Dan
> Re: Gradle Build [PREVIOUSLY] Re: Board feedback - Request discuss attic for
> River
> 12518 by: Phillip Rhodes
>
> Administrivia:
>
> -
> To post to the list, e-mail: dev@river.apache.org
> To unsubscribe, e-mail: dev-digest-unsubscr...@river.apache.org
> For additional commands, e-mail: dev-digest-h...@river.apache.org
>
> --
>
>
> From: Phillip Rhodes
> Subject: Re: Gradle Build [PREVIOUSLY] Re: Board feedback - Request discuss
> attic for River
> Date: July 1, 2020 at 10:10:29 PM EDT
> To: dev@river.apache.org
> Cc: Michael Sobolewski , dennis.re...@gmail.com
>
>
> A Gradle build would be nice. I'm willing to invest some time trying
> to help make it happen if need be. But I am curious.., it looks like
> someone started a Maven build a while back.. From what I can see it
> seems to maybe be incomplete, or just bit-rotted. But depending on the
> details of the state of that work, would there be any reason to prefer
> sticking with maven? (FSM help me, I can't believe I just said that in
> a public forum).
>
> I'm not the biggest Maven fan in the world, so I only raise this issue
> from the "can we use existing work instead of starting from scratch"
> perspective.
>
>
> Phil
>
>
>
