beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4744) Jars are overwritten during release with -Ppublishing
Date Thu, 09 Aug 2018 23:46:00 GMT


ASF GitHub Bot logged work on BEAM-4744:

                Author: ASF GitHub Bot
            Created on: 09/Aug/18 23:45
            Start Date: 09/Aug/18 23:45
    Worklog Time Spent: 10m 
      Work Description: udim commented on issue #5936: [BEAM-4744] Enable parallel publishing/release
   I added a special `publish` property to JavaNatureConfiguration so that those examples
project would not be published.
   What empty project was being published? I'm curious.

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:

Issue Time Tracking

    Worklog Id:     (was: 133399)
    Time Spent: 1.5h  (was: 1h 20m)

> Jars are overwritten during release with -Ppublishing
> -----------------------------------------------------
>                 Key: BEAM-4744
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Mark Liu
>            Assignee: Luke Cwik
>            Priority: Blocker
>             Fix For: 2.6.0
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
> +cc [~pabloem] [~boyuanz] [~lukecwik]
> Few jars (*-shaded.jar and *-tests.jar) are missing if I run `./gradlew -Ppublishing
> However, I can get them through assemble and shadowJar. For example, `./gradlew :beam-sdks-java-core:assemble
> This could be the reason why we can't run parallel build during release.

This message was sent by Atlassian JIRA

View raw message