-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support using the library in a non-springboot project #23
Labels
Comments
BGehrels
added a commit
that referenced
this issue
May 22, 2017
…hout any spring or third party tool dependency, one spring boot starter and one, that ties them all together
BGehrels
added a commit
that referenced
this issue
May 22, 2017
BGehrels
added a commit
that referenced
this issue
May 23, 2017
BGehrels
added a commit
that referenced
this issue
May 24, 2017
…it obvious that we had an off-by-one-error here
ePaul
added a commit
that referenced
this issue
May 24, 2017
#23 Support using the library in a non-springboot project
Part of this was done in #33. We want to collect some experience with this before we document how it needs to be used (and possibly add missing parts). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have some legacy spring-based projects which are not springboot-compatible (e.g. deployed to an existing Tomcat). It would be nice if we could use the library there too, maybe with some more manual configuration instead of the autoconfiguration.
I imagine that we would need to:
The text was updated successfully, but these errors were encountered: