Cliffred van Velzen

> Thanks for reporting this, I can reproduce it. It's indeed related to #564. Not sure about #638, since Kotlin (probably) doesn't compile its sealed classes down to Java's sealed...

Is there any sort of timeline for this epic?

> Apparently something changed with sealed classes in 1.7. > > However, I couldn't find anything in the release notes: the only mention of sealed classes is that non-exhaustive sealed...

I've locally tried a to solve it in a hacky way to see if it would work, by adding an extra if statement to https://github.com/mockk/mockk/blob/02a49b2f3639e066ff96d35a160bf301fe0bbb00/agent/jvm/src/main/kotlin/io/mockk/proxy/jvm/ProxyMaker.kt#L98 ```kotlin runCatching { if (clazz.isSealed)...

I'll try to create a test and look at your comment some time this week.

I've added a test, see https://github.com/cliffred/axion-release-plugin/commit/f7c6b4c28f4ddc8f2949984242c032b7043eee84 But I'm not sure how to handle the PushReleaseTask and HookContext as they also do pushing, and at that time you don't know the...

@bgalek Last time I stumbled upon the problem of handling pushing in PushReleaseTask and HookContext. I can't remember the exact details, but I will look at again this weekend.

We have the exact same need. Would it be possible to overload the versionCreator closure so it can also take just the versionContext? VersionContext contains all the information you need...

I had the exact same problem. I also see that `org.glassfish.hk2.osgi-resource-locator` is in 'STARTING' state, but that's not the problem. The problem is that `org.glassfish.jersey.core.jersey-common` is not ACTIVE, instead it...