Edoardo Luppi

Was looking at open issues before trying out Kotest. The fact `generateTypeScriptDefinitions` doesn't work is a major blocker for me.

@laeubi currently, if I'm not mistaken, Tycho resolves dependencies in `AbstractMavenLifecycleParticipant#afterProjectsRead`. Is this changed in the new resolver? Asking because if this is changed I need to revisit IntelliJ IDE...

Yeah, just tested it out. Target Platform dependencies are not resolved anymore. So one has to go back to the `classic` resolver when importing in the IDE (as the IDE...

@laeubi maybe the immediate resolution can be offloaded to a third party. When I setup the Maven container in IJ I can override the Tycho lifecycle participant, if it has...

@laeubi > Why not register an own one then? Keep in mind this is only for importing, the actual build process won't be touched. > this is a very costly...

This is the reason I'm still using `kotlin.test`. What I'm missing there tho is https://youtrack.jetbrains.com/issue/KT-49141 @krzema12 feel free to upvote it.

Hey everyone! I'm interested in prioritizing production branches over PRs. This seems to do it, any news?

@mPokornyETM it's just strange this was removed in the commit mentioned above. The alternative plugins do not do the same at all.

@laqua-stack it's very strange. ``` java.lang.ClassNotFoundException: com.intellij.openapi.vcs.VcsListener ``` That class is part of the Platform itself, and it should always be present. It must be related on how Gateway load...

@maicol07 @laqua-stack could you try this snapshot build? I've removed references of VCS-related classes at startup. See https://github.com/lppedd/idea-conventional-commit/commit/6bba450a1aa4f077ae806adc3700be880f3ab46f [idea-conventional-commit-0.21.1.zip](https://github.com/lppedd/idea-conventional-commit/files/11009244/idea-conventional-commit-0.21.1.zip)