Lower our dependency to Spring Security #858
Comments
sbegaudeau
added a commit
that referenced
this issue
Dec 4, 2021
All our representation event processor are connected to Spring Security while we have no reason to do so. All those dependencies have now been removed and the code has been simplified. The SubscriptionManager is now in charge of the canBeDisposedSink of all the representation event processor which removes both a field and a method from all the representation event processor Bug: #858 Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau
added a commit
that referenced
this issue
Dec 4, 2021
All our representation event processor are connected to Spring Security while we have no reason to do so. All those dependencies have now been removed and the code has been simplified. The SubscriptionManager is now in charge of the canBeDisposedSink of all the representation event processor which removes both a field and a method from all the representation event processor Bug: #858 Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau
added a commit
that referenced
this issue
Dec 4, 2021
All our representation event processor are connected to Spring Security while we have no reason to do so. All those dependencies have now been removed and the code has been simplified. The SubscriptionManager is now in charge of the canBeDisposedSink of all the representation event processor which removes both a field and a method from all the representation event processor Bug: #858 Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau
added a commit
that referenced
this issue
Dec 7, 2021
All our representation event processor are connected to Spring Security while we have no reason to do so. All those dependencies have now been removed and the code has been simplified. The SubscriptionManager is now in charge of the canBeDisposedSink of all the representation event processor which removes both a field and a method from all the representation event processor Bug: #858 Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau
added a commit
that referenced
this issue
Dec 7, 2021
All our representation event processor are connected to Spring Security while we have no reason to do so. All those dependencies have now been removed and the code has been simplified. The SubscriptionManager is now in charge of the canBeDisposedSink of all the representation event processor which removes both a field and a method from all the representation event processor Bug: #858 Signed-off-by: Stéphane Bégaudeau <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to help reuse Sirius Components more easily in other applications where Spring Security is not needed, we should remove some of our dependencies to this framework. It is not useful to use Sirius Components.
The text was updated successfully, but these errors were encountered: