[
https://issues.apache.org/jira/browse/BEAM-4744?focusedWorklogId=133731&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-133731
]
ASF GitHub Bot logged work on BEAM-4744:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Aug/18 18:01
Start Date: 10/Aug/18 18:01
Worklog Time Spent: 10m
Work Description: udim commented on issue #5936: [BEAM-4744] Enable
parallel publishing/release
URL: https://github.com/apache/beam/pull/5936#issuecomment-412160172
Yeah, this is regarding your changes in settings.gradle and the comment:
> the usage of :runners:google-cloud-dataflow-java:examples and
examples-streaming. This was creating an empty project that was being published
which was causing issues when attempting to perform a release.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 133731)
Time Spent: 1h 50m (was: 1h 40m)
> Jars are overwritten during release with -Ppublishing
> -----------------------------------------------------
>
> Key: BEAM-4744
> URL: https://issues.apache.org/jira/browse/BEAM-4744
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Mark Liu
> Assignee: Luke Cwik
> Priority: Blocker
> Fix For: 2.6.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> +cc [~pabloem] [~boyuanz] [~lukecwik]
> Few jars (*-shaded.jar and *-tests.jar) are missing if I run `./gradlew
> -Ppublishing :publishToMavenLocal`.
> However, I can get them through assemble and shadowJar. For example,
> `./gradlew :beam-sdks-java-core:assemble :beam-sdks-java-core:shadowJar`.
> This could be the reason why we can't run parallel build during release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
