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

Added gem 'hydra-head' to Gemfile #80

Closed
wants to merge 1 commit into from

Conversation

yvoloshin
Copy link

I found that gem 'hydra-head' had to be in the Gemfile in order for hydra-jetty to start successfully. Without hydra-head in the Gemfile, I would get "Unable to move tmp/jetty_generator/hydra-jetty-master into jetty/ Operation not permitted - (tmp/jetty_generator/hydra-jetty-master, jetty)" when I tried to run the hydra-jetty generator. With hydra-head in the Gemfile, this problem was solved. I tried this after seeing the instructions for hydra-head installation at https://github.com/projecthydra/hydra-head.

I found that gem 'hydra-head' had to be in the Gemfile in order for hydra-jetty to start successfully. Without hydra-head in the Gemfile, I would get "Unable to move tmp/jetty_generator/hydra-jetty-master into jetty/ Operation not permitted - (tmp/jetty_generator/hydra-jetty-master, jetty)" when I tried to run the hydra-jetty generator. With hydra-head in the Gemfile, this problem was solved. I tried this after seeing the instructions for hydra-head installation at https://github.com/projecthydra/hydra-head.
@mjgiarlo
Copy link
Member

Hi, @yvoloshin. The purpose of the Hydra gem is to wrap a bunch of other dependencies, so while this fixes the behavior for you, I think we should pursue fixing this elsewhere. Thoughts on this, @jcoyne @jeremyf @dchandekstark?

That said, thanks for the pull request! Always glad to see a pull request from someone who's not submitted one to the Hydra community before. In order for us to merge code from you in the future, we'll need to have signed Contributor License Agreements (CLAs) on file for you as an individual and your institution. You can read more about our CLA processes here:

https://wiki.duraspace.org/display/hydra/Hydra+Project+Intellectual+Property+Licensing+and+Ownership

The process itself is fairly simple -- you just need to print out the Hydra Project individual CLA (iCLA) and sign it and then send it to [email protected]. Same for the corporate CLA (cCLA) but that document must be signed by someone who has signatory authority for your institution. Let me know if you have any questions about this process, and I'd be happy to help.

@mjgiarlo
Copy link
Member

DO NOT MERGE. CLA required.

@dchandekstark
Copy link
Contributor

@mjgiarlo Agree that this should be fixed elsewhere, if possible.

@yvoloshin
Copy link
Author

That makes sense, @mjgiarlo. I'll make sure to sign the CLA next time I contribute. Did you also see the issue (#79) I sent in?

@mjgiarlo
Copy link
Member

Hi, @yvoloshin -- no, I missed #79. I recommend sending that to the hydra-tech mailing list where more eyes are sure to see it. Thank you for writing it up!

@yvoloshin
Copy link
Author

Thank you for the suggestion @mjgiarlo. I posted it on the mailing list.

@jcoyne jcoyne closed this Feb 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants