Louis CAD

I suggest that you hardcode the version for these private dependencies, because investigating that issue further is not in our current priorities. I'm reopening this issue so we remember to...

You should not use version ranges `+` because it makes builds not really reproducible, and can break future builds. FYI, `de.fayard:dependencies` will be deprecated (with a replacement). The API is...

FYI @DanySK , since refreshVersions 0.9.5, running the `refreshVersions` task will also look for updates for refreshVersions itself, and will add available updates comments and migration preparation automatically in the...

There's no way to ensure the dependencies have been added by a plugin or by code in the build files. That means there's a need for rules for every case...

I think this issue is not happening with the new `refreshVersionsMigrate` Gradle task. I think we'll soon drop the original fully manual migration task in favor of the aforementioned `refreshVersionsMigrate`...

I think Ktor2 version key rules were also forgotten. I'm adding them back.

Hello, if you want, we can look at this together in a pair-programming session so you'll get to understand how refreshVersions works, at least for the automatic migration system.

Did you try that? ``` org.protelis:* ^^^^^^^^ ``` I think it'd suit your use case.

@DanySK About the order, the longest matching rule is considered to be the most specific and is therefore picked. Can you share the full maven artifact names of these dependencies...

I see you're the author of the library, @DanySK. Why did you go for a dot for the parser artifacts, and for a dash for the other artifacts? That seems...