> I totally expect some things to bubble up when we try to release with > Gradle, the tarball being one. I don’t think that’s a very big issue, but > if you have lots of “not very big” issues they do add up. >
Adding a tarball is literally 3-5 lines of code (you add a task that builds a tarball or a zip file from the outputs of solr/packaging toDir task)... The bigger issue with gradle is that somebody has to step up and try to identify any other issues and/or missing bits when trying to do a full release cycle. D.
