i guess the question then is, do we switch to gradle for 1.5? can you check in the gradle build file so we can all take a look?
-igor On Sun, May 1, 2011 at 8:20 AM, Juergen Donnerstag <juergen.donners...@gmail.com> wrote: > I'm not a gradle expert which is why I had to try this and that. But > my initial tests to create the ueber jars have now been successful. > > -Juergen > > On Fri, Apr 29, 2011 at 2:16 PM, Martin Grigorov <mgrigo...@apache.org> wrote: >> I'm interested to see how easy is to do what we weren't able to do with >> Maven: >> - create a new module which should: >> -- combine all the .class-es from -core, -util, -request (aka uber-jar) >> -- combine all -sources.jar from the above into one (uber-sources.jar) >> <<--- this is the reason to give up what we had in 1.5-RC1 >> -- combine all -javadocs.jar from the above into one (uber-javadocs.jar) >> >> >> On Fri, Apr 29, 2011 at 3:06 PM, Juergen Donnerstag >> <juergen.donners...@gmail.com> wrote: >>> 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 >>>> >>> >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> >
