Paweł Lipski

+1, same for the support for Python versions like: ```requirements pytest==7.0.1; python_version=="3.6" pytest==7.1.2; python_version>="3.7" pytest-mock==3.6.1; python_version=="3.6" pytest-mock==3.7.0; python_version>="3.7" ``` Currently it crashes on ``` Error while parsing package pytest-mock==3.6.1; python_version=="3.6"...

@kelloggm @kennknowles any progress on this one? I'm running into the same issue within `openjdk:11` Docker image, plugin v0.5.5, CF v3.5.0 :/

@xenoterracide yeah, I second the observation that CF increases the build time significantly... but still, the value added by the Framework is so significant in my assessment that it's worth...

> I consider 1+ minutes on 5 classes way too slow. Actually, you can share the specific Gradle configuration :thinking:

+1 for this issue... for yet another simple workaround, see https://github.com/VirtusLab/git-machete-intellij-plugin/pull/1013 (basically, treat `buildSrc/` as if it was a top-level project)

Well... if you could just override `toString` in `trait SqlMigration` :)

Hmmm same as in my implementation?... Possibly with `getName` instead of `getSimpleName` :thinking:

Hey @franciscolopezsancho (tagging you coz we know each other ;) )... any chance this might get resolved soon? 🙏🏻

Somehow 6.5.1 seems to work with Kotlin 1.6.20, dunno what changed in our setup in the meantime 😅 https://github.com/VirtusLab/git-machete-intellij-plugin/pull/1200

From a quick check of JaCoCo (which seems to be the standard for Java as of 2022), it looks that we'll need to use **offline instrumentation** (rather than the default...