:sdks:java:testing:expansion-service could be useful to publish for testing as well.
On Fri, Aug 30, 2019 at 3:13 PM Lukasz Cwik <[email protected]> wrote: > > Google internally relies on being able to get the POM files generated for: > :sdks:java:testing:nexmark > :sdks:java:testing:test-utils > > Generating the POM files currently relies on publishing being enabled for > those projects so could we keep publishing those two modules. Disabling the > others sounds fine to me. > > On Thu, Aug 29, 2019 at 9:41 PM Lukasz Cwik <[email protected]> wrote: >> >> I wanted to double check that we don't rely on this publishing inside Google >> for some reason. Will update this thread tomorrow. >> >> On Wed, Aug 28, 2019 at 7:11 AM Łukasz Gajowy <[email protected]> wrote: >>> >>> Hi all, >>> >>> I wanted to notify that in PR 9417 I'm planning to turn off publishing of >>> the following modules' artifacts to the maven repository: >>> >>> :runners:google-cloud-dataflow-java:worker:windmill >>> :sdks:java:build-tools >>> :sdks:java:javadoc >>> :sdks:java:testing:expansion-service >>> :sdks:java:io:bigquery-io-perf-tests >>> :sdks:java:io:file-based-io-tests >>> :sdks:java:io:elasticsearch-tests:elasticsearch-tests-2 >>> :sdks:java:io:elasticsearch-tests:elasticsearch-tests-5 >>> :sdks:java:io:elasticsearch-tests:elasticsearch-tests-6 >>> :sdks:java:io:elasticsearch-tests:elasticsearch-tests-common >>> :sdks:java:testing:load-tests >>> :sdks:java:testing:nexmark >>> :sdks:java:testing:test-utils >>> >>> AFAIK, the purpose of these modules is to keep related >>> tests/test-utils/utils together. We are not expecting users to make use of >>> such artifacts. Please let me know if you have any objections. If there are >>> none and the PR gets merged, the artifacts will no longer be published. >>> >>> Thanks! >>> Łukasz
