security-core | Symfony Security Component - Core Library | Authorization library

I think you question has been already answered; please, consider review this SO question.

You need to include the following dependency:

You have to use the information SLF4J provide you and back trace the dependency using dependency:tree and its includes option.

This message:

There’s a relatively new Gradle feature called “version catalogs”. With those you can centrally declare dependencies that you’d like to share between multiple projects of your build (or even between different builds).

In your concrete example, you’d add something like the following to your settings.gradle file:

I think problem about version, can you try this :

Upgrading from Grails 2.1.5 to 2.5.5 or 2.5.6 would give you Java 8 support. I have done this multiple times. I have also have upgraded from Grails 2 to Grails 3 or I would now recommend using Grails 4. If you are going to make the bigger jump from Grails 2 to 3 or 4. I would skip Grails 3 and instead goto Grails 4. Doing the upgrade from 2 to 4 would take additional time but about the same amount of time going from Grails 2 to 3. One of the biggest concerns is what plugins do you use that are no longer supported. This could be a problem even going to Grails 2.5.5 but is a bigger deal going to Grails 3 or 4.

Here I posted some wisdom on going from Grails 2 to Grails 4.

How to Upgrade Grails from Grails 2.4.4 to Grails 4.0.1?

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

Spring 3.2.0.RELEASE uses asm 4.0, which does not support Java 8 or higher.

Since Java 7 is not supported any more, you should upgrade Spring to the latest patch release:

That composer.json file is a bit of a mess. Some Symfony packages on 5.3, some even on 5.1, and many on 6.

Also you are controlling Symfony versioning from extra.symfony.require, and at the same time from the discrete version constraints. You include some packages that no longer exist on 6.0 (symfony/security-guard), and are missing some that should be installed on a 6.0 version.

It's simply not on an installable state.

I've managed to make it installable changing it like this:

First, you cannot upgrade Spring for Spring Boot as that is tied to a specific Spring major version. To upgrade Spring you would need to upgrade to a newer Spring Boot version.

Secondly, your dependencies are a mess. A lot of exclusions that aren't needed and additional dependencies that aren't needed either.

A cleaned up version