-
Notifications
You must be signed in to change notification settings - Fork 21
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
Release, release, release #5
Comments
I will update my forked spring-security project and include this code as well as the test sample in the next couple of days and see if Spring-Security officials will respond to a PR. I'm not sure though if I should rework the general query as commented in #4 beforehand though. |
Can we get it centrally uploaded to maven? This is a very useful project for Mongo DB |
And is this Apache 2.0 licensed? |
Whatever happened here? Should I be using this project or is it dead in the water now? |
@peavers I didn't receive any feedback from the spring-security team at all thus I consider it a lack of interest on their side. As the project as is uses the spring-namespace I did not release it. Furthermore, the state of code works with spring security 4.3. I think I still have a local branch on my laptop to upgrade to 5.x but a test failed and I haven't had time to investigate further. As of a recent job change I currently also have no active needs to release the code. As this project is open source though you can fork it and move on with it. |
How come this is not yet part of the official Spring Security release? Have you contacted anybody in the Spring community about it?
In case they are not willing to embrace this for whatever reason, can I suggest you release this independently, so that we can pull a dependency rather than building it locally?
The text was updated successfully, but these errors were encountered: