[
https://issues.apache.org/jira/browse/BEAM-5379?focusedWorklogId=637372&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-637372
]
ASF GitHub Bot logged work on BEAM-5379:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Aug/21 14:59
Start Date: 12/Aug/21 14:59
Worklog Time Spent: 10m
Work Description: lostluck commented on pull request #15323:
URL: https://github.com/apache/beam/pull/15323#issuecomment-897711988
The only other pre-comment is that there are tools that could automatically
handle the version upgrade in the import statements. It's probably only a
little different from the find and replace strategy...
This issue: https://github.com/golang/go/issues/32014 has a few comments
referencing a few community options, in the absence of a centralized tool.
https://github.com/marwan-at-work/mod
https://github.com/icholy/gomajor
https://github.com/nathanjcochran/upgrade
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 637372)
Time Spent: 8h 10m (was: 8h)
> 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: Daniel Oliveira
> Priority: P3
> Time Spent: 8h 10m
> 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.
> Edite June 2020: In particular for cross use with GoGradle, we can set
> options to avoid gradle's own locking system: See
> https://github.com/gogradle/gogradle/issues/304
> ```
> installDependencies.enabled = false
> resolveBuildDependencies.enabled = false
> ```
> And we'll likely need to ignore the advice for major versions past v2
> adopting modules:
> https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher
> which recommends that we increment the major version. This is mitigated by
> such a move yielding that first Go Modules version to be in line with the
> first Non Experimental version of the SDK, so users should do a manual update
> step for that. Unfortunate, but it's a hard signal that something has
> happened.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
