[ 
https://issues.apache.org/jira/browse/BEAM-4584?focusedWorklogId=113541&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-113541
 ]

ASF GitHub Bot logged work on BEAM-4584:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Jun/18 03:55
            Start Date: 20/Jun/18 03:55
    Worklog Time Spent: 10m 
      Work Description: kennknowles commented on issue #5683: [BEAM-4584] 
Migrate build_rules.gradle to buildSrc plugin
URL: https://github.com/apache/beam/pull/5683#issuecomment-398616540
 
 
   So, we have a job we can trigger "Run Gradle Publish" but that seems like 
something that should not exist. I guess if it is just a snapshot that will be 
wiped out it could be useful for PRs just like this one. But anyhow PTAL as I 
think this is pretty much alright and it is better to get it moving along as 
soon as possible after 2.5.0

----------------------------------------------------------------
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: 113541)
    Time Spent: 1h 50m  (was: 1h 40m)

> Use a "binary plugin" in buildSrc instead of "script plugin" in 
> build_rules.gradle
> ----------------------------------------------------------------------------------
>
>                 Key: BEAM-4584
>                 URL: https://issues.apache.org/jira/browse/BEAM-4584
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> This is a best practice recommended by the Gradle documentation. It is 
> expected to speed things up, and makes dependency management and testing 
> slightly better.
> In terms of code, it is not much different, though some things that were 
> previously implicit in the top-level groovy DSL will need to be made explicit 
> in the plugin definition.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to