I played a bit with gradle recently. - Transfered Wicket's build process which was fairly straight forward; compile, test, install. jetty:run etc. - eclipse project files generated seem to be ok - maven repositories to get artifacts - successfully installed a new snapshot in my local repo
I didn't test anything beyond though, especially not our release process. And I didn't look at report etc. -Juergen On Fri, Apr 29, 2011 at 11:35 AM, Martijn Dashorst <martijn.dasho...@gmail.com> wrote: > On Thu, Apr 28, 2011 at 9:10 PM, Igor Vaynberg <igor.vaynb...@gmail.com> > wrote: >> we tried to create the uber jar but it failed. maybe if we used >> something like gradle we couldve done it, but switching build systems >> just for this seems a little extreme. > > Not quite: I've had enough problems with Maven at $dayjob that I'm > considering dumping it for either gradle or buildr. While I haven't > looked at gradle in detail, I suspect it would make releasing Wicket a > bit simpler. > > It wouldn't necessarily break our support for Maven, just that we now > use another build system, but still deploy our artifacts to the maven > repo, including pom files. > > Martijn >
