This will list Spring-related issues that would be nice to resolve. Most are non-fatal and have little to do with the requirements of finding and listening to music. These are technical subtasks that are not of interest to users, but which will hopefully be resolved at some point in order to keep the server viable.
Background
In particular, the migration from Spring Boot 2.x to 3.x included a huge number of specification changes and changes in the direction of best practices. Jpsonic has jumped from Spring Boot 2.x used in Airsonic to 3.2 (it was necessary to skip 3.0 and 3.1 to match the Servlet Version of Tomcat/Jetty) .
To achieve a soft landing, it was necessary to make the correction difference as small as possible. As a result, less critical issues or issues with workarounds were temporarily omitted to be fixed and tested separately later.
- 3.3
2653
Log suppressed. There are two contents. Once resolved, log suppression will be removed.
[ ] #2632
False positive for Jettly's Alias Chaker. A good scenario would be to have this handled automatically between Spring and Jetty. If not, it is necessary to suppress false positives (although this is a little unlikely).
[ ] Fix for AuthenticationManager related
Consider removing the AuthenticationProvider bean. Alternatively, consider using the UserDetailsService in a manually instantiated DaoAuthenticationProvider.
- 3.2
To be honest, it's not that important... (If we can completely redesign the screen in the future, we won't need to do anything until then.)
[ ] #2581
- 3.0
When we delete DWR, the local repository disappears from Jpsonic. Most of the local repositories that existed in Airsonic have been resolved and removed. This is the last one. But it's just extremely troublesome.
Overview
This will list Spring-related issues that would be nice to resolve. Most are non-fatal and have little to do with the requirements of finding and listening to music. These are technical subtasks that are not of interest to users, but which will hopefully be resolved at some point in order to keep the server viable.
Background
In particular, the migration from Spring Boot 2.x to 3.x included a huge number of specification changes and changes in the direction of best practices. Jpsonic has jumped from Spring Boot 2.x used in Airsonic to 3.2 (it was necessary to skip 3.0 and 3.1 to match the Servlet Version of Tomcat/Jetty) .
To achieve a soft landing, it was necessary to make the correction difference as small as possible. As a result, less critical issues or issues with workarounds were temporarily omitted to be fixed and tested separately later.
- 3.3
2653
Log suppressed. There are two contents. Once resolved, log suppression will be removed.
- 3.2
To be honest, it's not that important... (If we can completely redesign the screen in the future, we won't need to do anything until then.)
- 3.0
When we delete DWR, the local repository disappears from Jpsonic. Most of the local repositories that existed in Airsonic have been resolved and removed. This is the last one. But it's just extremely troublesome.