Jetty

[Tom Zeller]

> On Aug 28, 2015, at 4:14 AM, Ian Young <ian at iay.org.uk> wrote:
> 
> 
>> On 28 Aug 2015, at 02:25, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> 
>> Is it time to start looking at Gradle?
> 
> Does anyone on the team have significant experience with it? I hate Maven with a fiery passion, so I'd be the last person to regret seeing it replaced. But the main reason I have problems with it is that it's often impenetrable and unredictable, and historically that kind of thing has a tendency to spawn replacements which are no better. Knowing that the cool kids all use Gradle now isn't particularly compelling (to me) on its own.
> 
> I'd like to hear a pitch from someone familiar with our current system who has actually used Gradle saying that (a) we can do all the same things in Gradle as we do in Maven and (b) we'd also get benefits X, Y and Z.

However long it would take to migrate from Maven to Gradle is probably almost as long as it would take for me to answer those questions. If Gradle could replace our use of Maven and Ant, great, but I think not, since we are really using Ant as our installation “UI” - not sure if Gradle offers better there. It seems we will want to produce Maven artifacts for awhile, so it seems “more work” to me to use Gradle to produce Maven artifacts than to use Maven to produce Maven artifacts, but maybe it’s that broken ;-)

As a minor note, whenever I import Spring projects into Eclipse to run along with the IdP/Jetty, I wish those projects, as source, would have Maven POMs so I don’t have to fool with Eclipse classpaths or build paths. So, one benefit to using Gradle might be easier development alongside Spring. But not Jetty, at least now.