Dependency Conflict: `flutter_map` Version Incompatibility

[Zambeel-Ltd]

First, I want to express my sincere gratitude for maintaining the flutter_map_marker_cluster package. It's a very valuable tool, and I appreciate your efforts in keeping it updated.

I've encountered a dependency conflict when trying to use flutter_map_marker_cluster version 1.4.0. The issue arises because:

flutter_map_marker_cluster >=1.4.0 depends on flutter_map ^7.0.0. My project is using a package that depends on flutter_map ^8.1.0. This results in a version solving failure, as there is a requirement for incompatible versions of flutter_map.

I'm writing to request that you consider upgrading the flutter_map dependency within flutter_map_marker_cluster to the latest version (currently 8.1.0). This would allow for better compatibility with projects that rely on the latest flutter_map releases.

Thank you for your time and consideration.

[pagetronic]

It's never good to rush on updates. Here we see that flutter_map has already released fixes..

A little patience ;)

[jbxbergdev]

Affected by this, too. Sure take the time you need. However as supposedly the majority of flutter_map users, we use it with a host of other extensions. The other projects publish updates/fixes that eventually require a flutter_map upgrade. We're currently stuck with that upgrade due to flutter_map_marker_cluster requiring an old flutter_map version. To the maintainers: Is there a specific incompatibility that would need to be solved when upgrading to flutter_map 8? Or could we just do a dependency override?

[aytunch]

Hi @lpongetti would you be kind enough to publish a new release supporting latest flutter map?

[Zambeel-Ltd]

@lpongetti if you are not able to give time to it. then you can respond one of us will create a PR.

[D-Azria]

Hi @lpongetti. First, thanks for everything you made. The PR for flutter_map 8 has been merged on main few weeks ago, but there's no new tag indicating a new version, so in pubdev we cannot have the modified package with updated pubspec. Can you make the new tag ? Thanks a lot.

[lpongetti]

Hi, I'm waiting for flutter_map_marker_popup to release the flutter_map 8 compatible version. For now you can import it like this: flutter_map_marker_cluster: git: url: https://github.com/lpongetti/flutter_map_marker_cluster.git ref: master

[scapin01]

Hi @lpongetti, you should temporary favor this fork for the compatible flutter_map_marker_popup (with flutter_map 8+): https://github.com/pablodelolmo/flutter_map_marker_popup At least all tests are green and the issue mentioned here is not present: https://github.com/fleaflet/flutter_map/issues/2038#issuecomment-2809224323 (The MarkerLayer has been adapted properly)

[fatihdurmaz]

Can you give a date for when it will be updated?

[FilipeOS]

@lpongetti flutter_map_marker_popup was updated, can this be updated too?

[FilipeOS]

@lpongetti bump

[FilipeOS]

@lpongetti please?

[houmanhafez]

bruh :/

[Zambeel-Ltd]

Hi @lpongetti, hope you're doing well! Just checking in—if you're currently busy and don't have time to work on this, feel free to leave a comment. One of us can create a PR, and then you can review and merge it when you're available.

[jithware]

@lpongetti thank you for all your efforts with this project! If you are unable to give this update attention, perhaps you would be willing to designate another one of your contributors the authority to merge changes and publish to pub.dev? A similar thing was happening with flutter_map in it's early stages and @JaffaKetchup (among others) took it over and have built it to the incredible project it is today. Just a thought.

[JaffaKetchup]

Also see fleaflet/flutter_map#2104 and its parent issue. Only constructive discussion is permitted. The last commit being only 2 months old is a good indication that this is not abandoned given that the average length between commits is also about the same length. We do appreciate, however, that not being published to pub.dev is an issue, and potentially keeping users on older versions of FM than necessary (which we want to avoid).

[usamasaleem1]

@lpongetti yo where ya at

[FilipeOS]

Another dead plugin that was so nice...

[iBelow]

another dead plugin, huh? the author is not going to do anything? there is a version lock there

[petodavid]

Can you please release the new version?

[JaffaKetchup]

Please remember that users can depend from Git/GitHub in the meantime. See https://dart.dev/tools/pub/dependencies#git-packages. You may need to place this in dependency_overrides rather than dependencies.

You can also subscribe or unsubscribe to this thread to get/lose notifications without commenting.

[jithware]

Because of a dependency conflict even when using the current master branch, I needed to fork this repository and make this dependency update.

Here are the steps performed:

1. Fork this repo
2. Update your project pubspec.yaml to use the forked flutter_map_marker_cluster repo

  flutter_map_marker_cluster: 
    git:
      url: "https://github.com/<username>/flutter_map_marker_cluster.git"

3. If there are any conflicts, update your forked flutter_map_marker_cluster pubspec.yaml as needed and push the changes to your fork

If you don't want to use a fork you could also just clone the repo locally and make the dependency changes there, then update your project pubspec.yaml (assuming the clone and your project are in the same parent directory):

   flutter_map_marker_cluster:
    path: ../flutter_map_marker_cluster

The advantage to using a fork is if this project goes long term unattended, and a forked maintainer chooses to do so, their fork could become the new maintained package.

[iBelow]

The only thing the author needs to do is add a tag and publish an update on pub.dev (without a tag it doesn’t work). That’s it — the problem with having to use workarounds like forking three separate packages would be solved.

So why hasn’t the author done this for half a year and just keeps closing issues about this problem instead?

[lpongetti]

Done