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

Updates fcrepo-camel-toolbox to work with Fedora 5.x. #142

Closed

Conversation

dbernstein
Copy link
Contributor

Updates fcrepo-camel-toolbox to work with Fedora 5.x.


JIRA Ticket: https://jira.duraspace.org/browse/FCREPO-2787

  • Other Relevant Links (Mailing list discussion, related pull requests, etc.)

What does this Pull Request do?

  1. Adds support for authentication to the integration tests.
  2. Fixes all broken unit tests.
  3. Updates fcrepo 5 and related dependencies.

What's new?

Authentication support for the integration tests, both in the test code as well as the jetty test server, is the main change. Otherwise just fcrepo4 and fcrepo-java-client dependency updates.

How should this be tested?

This PR ensures that the unit and integration tests are passing. Be sure to build the latest fcrepo-camel locally before building this PR. I have not done any hands on testing at this point: this PR simply ensures that all the tests are passing.

Interested parties

@peichman-umd, @awoods, @birkland

1. Adds authentication to the integration tests.
2. Fixes all broken unit tests.
3. Updates fcrepo 5 and related dependencies.

Resolves:  https://jira.duraspace.org/browse/FCREPO-2787
@peichman-umd
Copy link
Contributor

@dbernstein Looks like we need to get Travis to use the latest fcrepo-camel?

@dbernstein
Copy link
Contributor Author

I'm closing this PR: we're focusing on fixing https://github.com/dbernstein/fcrepo-camel-toolbox/tree/update-fcrepo-parent-pom.

@dbernstein dbernstein closed this Feb 7, 2019
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

Successfully merging this pull request may close these issues.

2 participants