[
https://issues.apache.org/jira/browse/THRIFT-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426927#comment-16426927
]
Brian Shannan commented on THRIFT-4542:
---------------------------------------
Our problem is we have a lot of code (both library references and generated
code) across many codebases that would take several people a few days to update
all of them, which is a pretty significant chunk of time. Is it possible to
have a copy put up at the old location with a disclaimer that any new code
won't be pushed there, so you need to switch to the new repo location?
This is pretty inconvenient as no notice that I could find was given to
consumers that a change would be needed.
> git.apache.org/thrift.git unavailable
> -------------------------------------
>
> Key: THRIFT-4542
> URL: https://issues.apache.org/jira/browse/THRIFT-4542
> Project: Thrift
> Issue Type: Bug
> Components: Documentation, Go - Compiler, Go - Library, PHP - Library
> Reporter: Brian Shannan
> Priority: Critical
>
> https://issues.apache.org/jira/browse/INFRA-16287 appears to have moved the
> thrift repo from git.apache.org/thrift.git to a new location, without leaving
> a copy of the repository at the old location. This broke all the imports of
> thrift in go generated code, as it references git.apache.org/thrift.git, as
> well as library code we have to interact with thrift. This can be changed
> through a flag in the generator, but due to the nature of go all imports of
> thrift have to be from the same url (otherwise the go compiler thinks they're
> different types), making this a pain to upgrade across multiple codebases and
> instances of generated code.
>
> A copy of the thrift repo at it's current state should be put back at
> git.apache.org so existing go code would continue to work until consumers can
> switch imports to the new repository
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
