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
Enable Fedora Resource Index by fixing logging jar conflict. #30
Conversation
…ource Index on by default.
@awead Hello! Since I'm modifying hydra-jetty master, and master has Fedora 3.7, I tested against the fedora-3.8 branch of active_fedora and everything passed. (As opposed to testing against active_fedora master, which references hydra-jetty/fedora-4/master). Hopefully this was the right thing to do. FYI: Current hydra-jetty master fails when run against active_fedora master, likely because of Fedora 4 differences. Is there anything else that I should check? (Or change?) I made a very minor commit to projectblacklight/blacklight a while back, but I don't think that I've ever signed a committer's license agreement with projecthydra. Happy to do so! |
@elo2112 That should be fine. However, we will need a signed iCLA (individual committer's license agreement). Sorry if this seems over the top, but it's to ensure all our code is Apache2 and therefore freely shareable to any and all. It's a pretty easy process. Send an email to |
@awead I believe @elo2112 is at Columbia, so they already have an institutional CLA, but he'll still need and individual one. |
@awead I can confirm the Columbia affiliation- I coerced this PR out of him. Sorry I forgot about the CLA, @elo2112 |
No problem! Just sent that email to legal. Thanks, everyone. |
awesome! thanks @barmintor @elo2112 |
Still working on getting approval from legal, but I'm going to close this pull request per a good recommendation from @barmintor (since the branches of this project just changed). I'll re-pull in a moment, referencing this request in a new comment. |
So I'm running into an issue after re-implementing the changes in the 7.x-stable branch. At Columbia, we're running Fedora (in tomcat) with the risearch enabled -- no problems. But even before my changes, I'm seeing a new error (included below) whenever I go to /fedora/risearch. I'm looking into it, but if anyone knows what might have changed between 3.7 and 3.8, I'd appreciate any thoughts. Thanks. org.eclipse.jetty.servlet.ServletHolder$1: java.net.MalformedURLException: ri/index.xsl |
It looks like the RI resources were deleted from the fedora home directory On Fri, Dec 5, 2014 at 11:54 AM, Eric O notifications@github.com wrote:
|
@elo2112 Be sure to rebase your branch off of hydra-jetty/7.x-stable. I just pushed some new commits up there last night. |
@awead Re-forked altogether because it was fast and easy, so I've got the latest ones. @barmintor and I are going to look into the missing RI resource issue and then I'll create a new pull request. |
Closing because this PR was superseded by #38. |
Also turn Resource Index on by default.