[
https://issues.apache.org/jira/browse/BEAM-5379?focusedWorklogId=286089&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-286089
]
ASF GitHub Bot logged work on BEAM-5379:
----------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jul/19 17:38
Start Date: 31/Jul/19 17:38
Worklog Time Spent: 10m
Work Description: lostluck commented on issue #9085: [BEAM-5379] Add go
modules
URL: https://github.com/apache/beam/pull/9085#issuecomment-516948427
Running the Post Commit makes it look like there's a bit more baking to be
done WRT the integration tests, but this approach is still promising!
https://builds.apache.org/job/beam_PostCommit_Go_PR/58/console
It looks like the integration tests are doing something weird, causing some
recursion...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 286089)
Time Spent: 4h (was: 3h 50m)
> Go Modules versioning support
> -----------------------------
>
> Key: BEAM-5379
> URL: https://issues.apache.org/jira/browse/BEAM-5379
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Robert Burke
> Assignee: Robert Burke
> Priority: Major
> Time Spent: 4h
> Remaining Estimate: 0h
>
> This would make it easier for non-Go developers to update and test changes to
> the Go SDK without jumping through hoops to set up Go Paths at first.
> Right now, we us the gogradle plugin for gradle to handle re-producible
> builds. Without doing something with the GO_PATH relative to a user's local
> git repo though, changes made in the user's repo are not represented when
> gradle is invoked to test everything.
> One of at least the following needs to be accomplished:
> * gogradle moves to support the Go Modules experiment in Go 1.11, and the SDK
> migrates to that
> * or we re-implement our gradle go rules ourselves to use them,
> * or some third option, that moves away from the GO_PATH nit.
> This issue should be resolved after deciding and implementing a clear
> versioning story for the SDK, ideally along Go best practices.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
