Okay, I've tried to spread that link a little on social media as well. Please do some experimentation. Especially those of you that use or know more esoteric things about the build. The basics are pretty solid, most have been working for months now, it's the corners and crannies that I'm more concerned about. You could have built and run tests a few months ago and said, nice, it's working, but then I've done 10,000 things since then that were necessary. You may easily not realize things are a problem until you really dig into something.
The more that devs can start trying out Gradle now, the less overlap of the two build systems we will need. The idea of the overlap is that it will almost force many of us to start trying things out - at which point we will start to understand any key things that are missing, key problems or bugs, etc. If I just make the switch and let the cards fall were they may, those cards are almost certainly going to be very disruptive and annoying to a lot of people. It will also give us a chance to start rolling CI and other tools over to using the Gradle build while ant+ivy are still available and in charge. I don't think it's a great idea to try and do this all at one moment, that will be difficult to coordinate and be more disruptive to less interested devs. We would like to keep the dual build situation contained and short though. That's why I have a plan to pull out if we don't make enough progress by a month or twos time (closer to a month). If we have enough experimentation ahead of time, the overlap can be very short - we start moving things like jenkins jobs over and when we are done and confident the world is not ending, we make some adjustments so that gradle owns the build (eg the dependency tree) and then remove ant+ivy+maven. Some things like the smoke tester and what not *can* come shortly after we switch I think - we have until the 9 release to truly get everything in order (keeping in mind that we are still developing so some things are still critical). But we need CI and other basics all moved over when we flip the ownership switch. - Mark On Sun, Sep 15, 2019 at 12:28 PM Mark Miller <markrmil...@gmail.com> wrote: > I've started to put together a little guide to help people ramp up here: > https://cwiki.apache.org/confluence/display/SOLR/Intro+to+the+Gradle+build > > On Sat, Sep 14, 2019 at 9:09 PM Mark Miller <markrmil...@gmail.com> wrote: > >> https://issues.apache.org/jira/browse/SOLR-13452 >> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle. >> >> Hey all. >> >> Here is my Lucene and Solr 'move to Gradle' plans. >> >> * I plan on trying to commit the Gradle build by 9/30 >> * In the meantime I'll do a bit more work on packaging, publishing, and >> dependencies. >> * It would be great if others could start digging in a bit as well. >> * I plan to try and sidecar Gradle to begin with. Once that happens, I >> really need others to start digging in as we have a lot to do (switch ci >> and other tools to the new build, figure out new release docs and issues, >> finish the Solr documentation module (I'll try and get to that earlier than >> later), and generally make things pleasant across as many dev envs as we >> can. >> * Beyond that, there will likely be a longer tail of smaller issues or >> missing things even after we make the switch. >> * I'll put some effort into the side car experiment for another month or >> two perhaps (maybe not much in November) >> * If things are not looking like we will be able to flip the switch, I'll >> look at pulling out Gradle. >> >> - Mark >> > > > -- > - Mark > > http://about.me/markrmiller > -- - Mark http://about.me/markrmiller
