Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ory vs ory-am #414

Closed
pbarker opened this issue Apr 11, 2017 · 4 comments
Closed

ory vs ory-am #414

pbarker opened this issue Apr 11, 2017 · 4 comments

Comments

@pbarker
Copy link
Contributor

pbarker commented Apr 11, 2017

Hey so I was trying to implement the rest of the Discovery code that you had started with #379. I noticed you all moved repositories from ory-am to ory, can I change the go imports to reflect that or were you waiting for some reason?

@aeneasr
Copy link
Member

aeneasr commented Apr 11, 2017

The golang codebases will not be moved, to keep BC. Only new repos will use ory. So keep using ory-am where it says so in the readme :)

@pbarker
Copy link
Contributor Author

pbarker commented Apr 11, 2017

hmm thats a bit odd, how are you syncing them? I made modifications to the oauth2 package and now I need to use those modifications in cmd, I don't see the repo under ory-am anymore, are you just renaming locally?

@aeneasr
Copy link
Member

aeneasr commented Apr 11, 2017

no, there's a redirect: https://github.com/ory-am/hydra

@pbarker
Copy link
Contributor Author

pbarker commented Apr 11, 2017

ok, I can make that work, this is just where Go's absolute imports are no fun, thanks for the help 👍

@pbarker pbarker closed this as completed Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants