Re: Gradle Status [April 11]

Great thanks for that! Makes perfect sense. On Wed, Apr 11, 2018 at 7:59 PM, Kenneth Knowles wrote: > There are plenty of technical hurdles since Bazel is best suited to an > isolated monorepo. We could probably have overcome those problems with > effort. I got through a few of

Re: Gradle Status [April 11]

just created one https://issues.apache.org/jira/browse/BEAM-4057 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book 2018-04-12 18:15 GMT+02:00 Ahmet Altay : >> Found another blocker in current artifacts creations: there is not > pom.xml and

Re: Gradle Status [April 11]

> Found another blocker in current artifacts creations: there is not pom.xml and pom.properties in META-INF. This is used by tools + libraries + integrations so it is quite important to not break it Romain, is there a JIRA for this issues? If not could you create one please? On Thu, Apr 12, 2018

Re: Gradle Status [April 11]

Nice ! thanks Kenn Le mercredi 11 avril 2018 à 18:21 +, Kenneth Knowles a écrit : > Initial Nexmark+Gradle run is in, though a hiccup in the Spark runner + Netty > has been introduced since yesterday. > Etienne mentioned he has worked toward setting up periodic runs on all > runners, so this

Re: Gradle Status [April 11]

Found another blocker in current artifacts creations: there is not pom.xml and pom.properties in META-INF. This is used by tools + libraries + integrations so it is quite important to not break it. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book 2018-04-12 0:59

Re: Gradle Status [April 11]

There are plenty of technical hurdles since Bazel is best suited to an isolated monorepo. We could probably have overcome those problems with effort. I got through a few of them in the short sprint I did. Ultimately it was a community-driven decision: more people (as in "more than just me" :-)

Re: Gradle Status [April 11]

Is there a document or similar outlining the decision behind Gradle over Bazel? For purely intellectual curiosity I’m curious what tradeoffs/benefits were considered when evaluating the two or if it was more a matter of community/contributor familiarity. I found this thread which seems to imply

Re: Gradle Status [April 11]

Initial Nexmark+Gradle run is in, though a hiccup in the Spark runner + Netty has been introduced since yesterday. Etienne mentioned he has worked toward setting up periodic runs on all runners, so this should help get us towards that. We'll probably prefer to build standalone fat jars for

Gradle Status [April 11]

Thanks everyone for the continued effort towards the Gradle migration. As a high-level summary of our progress since Friday: we have a viable build, with a number of minor issues that we're still working out. Please take a look at the new documentation in our contribution guide and log any bugs