FlexibleAdapter v5.1.0 update did not change the version number

[huzhicheng1993]

FlexibleAdapter v5.1.0 was released on Oct 21, 2018, and re-released as v5.1.0 on Mar 08, 2026.
Why is it an overwrite version rather than a version number change?
This could cause old projects to fail to build, forcing an upgrade.

[davideas]

Hello @huzhicheng1993, JCenter is not reachable anymore, if you try to get the version of 2018 you end with "Resource not found".
The library couldn't be simply move from JCenter to Maven Central because it does not exist. The rebuild with same version, was the only solution to make finally downloadable the library from Maven Central that requires a complete new system upload and specific signatures. How can it cause the forcing the upgrade if the code is the same for 5.1.0.
The other older versions were lost anyway with JCenter shutdown years ago.

[huzhicheng1993]

hello @davideas

However, after clearing the local cache today, it was pulled to version 5.1.0 with minCompileSdk set to 35.
Can we lower the minCompileSdk version to be consistent with the previous version?

[davideas]

Oh 🫤 so it took the targetSdk for the aar, not the minSdk in the manifest.
How do you suggest to proceed with the versioning? since Maven doesn't allow to delete it anymore. I would prefer to not change the version.

PS. That's the new Android Studio and various compilation errors, pushed me use the latest versions. And in fact while trying to lower things all go in conflict again. I will see what to do.

[davideas]

I was able to upgrade the sample app to SDK 35 and Java21 with not much effort. What is the effort for you to upgrade as well? I have read that, up to SDK 33 the effort of upgrading should be minimal.

However I finally made a new build with minSdk 1, it wasn't easy. Also, I asked a clean in Maven Central to not change 5.1.0 version I hope they will accept. If they don't we will have to find another solution.

To unblock you I did a snapshot.
Use this url and version:

maven { url "https://central.sonatype.com/repository/maven-snapshots/" }`
implementation 'eu.davidea:flexible-adapter:5.1.0-SNAPSHOT'

[huzhicheng1993]

I was able to upgrade the sample app to SDK 35 and Java21 with not much effort. What is the effort for you to upgrade as well? I have read that, up to SDK 33 the effort of upgrading should be minimal.

However I finally made a new build with minSdk 1, it wasn't easy. Also, I asked a clean in Maven Central to not change 5.1.0 version I hope they will accept. If they don't we will have to find another solution.

To unblock you I did a snapshot. Use this url and version:

maven { url "https://central.sonatype.com/repository/maven-snapshots/" }`
implementation 'eu.davidea:flexible-adapter:5.1.0-SNAPSHOT'

Hello @davideas,

Thank you for your efforts regarding this issue. Currently, my project is using compileSdkVersion=33. This problem only manifests when the compileSdkVersion is lower than minCompileSdkVersion=35.

Due to the specific nature of my project, it is not feasible for me to modify the targetSdkVersion or compileSdkVersion directly, as these settings are controlled by the host application.

My recommendation is as follows: First, roll back the version released on March 8, 2026 (which you have already done). Subsequently, any further changes should be accompanied by a version number update; directly overwriting and releasing the original version is not advisable.

If the rollback is successful, I would appreciate it if you could provide an update; otherwise, I will have to look for an alternative solution. Thank you again.

[davideas]

Ok understood. Does the snapshot version I prepared work in your app? If yes, I am ready to republish with the support of Maven Central: they will agree to clean it at certain conditions, their policy is pretty strict.

[huzhicheng1993]

the snapshot version

Hello @davideas
The snapshot version can be compiled and used normally, you can republish it. Thank you

[davideas]

Hello @huzhicheng1993, the library is available in Maven Central again.
I added more explanations and release notes here: 5.1.0-2026