Louis CAD
Louis CAD
@NikkyAI I fixed what I broke on the main branch, you can undo the changes you did to work that around in this PR.
If you merge latest main again, the issue will go away.
The migration task is currently not designed to be perfect, it does, say, 90% of the job, and you do the remaining 10%. Now, the next version (release in a...
Re-opening because I think we want to avoid the migration task to mess with this as @toddobryan pointed out.
Nice find, this is definitely something to specify in the doc. Plugins do not support version rules, but, there's already a solution for your use case: ``` version.io.gitlab.arturbosch.detekt..detekt-formatting=plugin.io.gitlab.arturbosch.detekt ``` I'm...
It might be a poorly handled case now that I think about it. I'll test it later and let you know, note taken.
@DanySK This works: Version key rule: ``` io.gitlab.arturbosch.detekt:detekt(-*) ^^^^^^ ``` `version.properties` file: ``` plugin.io.gitlab.arturbosch.detekt=version.detekt version.detekt=1.9.0 ## # available=1.9.1 ## # available=1.10.0-RC1 ```
Making refreshVersions able to work partially when some repos are timing out, or failing in other ways is planned, I'll keep you updated.
Relates to #468
Hello, You say: > I'd like to stick to my own way of declaring dependency versions Why?