There’s a comment on that wiki page that I was going to ask about. Specifically it references the maven-publish plugin [1]. Is the team amenable to adding it to the parent build file? It makes it a lot easier to incorporate locally built beam artefacts into a local maven project. Obviously not globally reproducible but useful for people wanting to submit changes to beam and then test them in their own project.
1 - https://docs.gradle.org/current/userguide/publishing_maven.html#publishing_maven:tasks On Sat, May 23, 2020 at 15:17, Thomas Weise <t...@apache.org> wrote: > Hi Jacek, > > Most of the developer documentation can be found on the cwiki, in this case > > https://cwiki.apache.org/confluence/display/BEAM/Gradle+Tips > > To build just a runner, for example, Flink: > > ./gradlew :runners:flink:1.10:job-server:runShadow > > > Thomas > > On Sat, May 23, 2020 at 10:29 AM Jacek Laskowski <ja...@japila.pl> wrote: > >> Hi, >> >> I've been wondering how the devs build Beam locally. I'm new to gradle >> and can't seem to find it in the docs [1]. >> >> I thought the following would be enough, but turns out it executes go-, >> website- and python-related tasks among others. >> >> ./gradlew build -x test >> >> I thought about disabling the tasks I don't want and ended up with the >> following: >> >> ./gradlew build -x test -x check -x website -x docker -x >> :sdks:python:setupVirtualenv >> >> but that still builds other projects I don't need and so I doubt if -x's >> is the way to go. There must be a more clever approach. What's that? Please >> help. Thanks. >> >> [1] https://beam.apache.org/contribute/ >> >> Pozdrawiam, >> Jacek Laskowski >> ---- >> https://about.me/JacekLaskowski >> "The Internals Of" Online Books <https://books.japila.pl/> >> Follow me on https://twitter.com/jaceklaskowski >> >> <https://twitter.com/jaceklaskowski> >> > -- Nathan Fisher w: http://junctionbox.ca/
