Paweł Lipski
Paweł Lipski
AFAICS the IntelliJ is executed just under the current JDK: ``` $ ps -f 78132 UID PID PPID C STIME TTY TIME CMD 501 78132 1 0 9:48pm ?? 0:37.97...
``` MacBook Pro, 2019 macOS Ventura 13.0.1 Plugin version: v3.2.2 Target IDE version: 2022.3 ``` ``` $ java -version openjdk version "17.0.5" 2022-10-18 LTS OpenJDK Runtime Environment Corretto-17.0.5.8.1 (build 17.0.5+8-LTS)...
There's only `probe.paths.logExport`, somewhat related... but apparently nothing to avoid the removal completely. Esp. important in local runs — to inspect the local contents easily, and to avoid errors like:...
junit-driver depends on JUnit 4 (https://github.com/VirtusLab/ide-probe/blob/master/project/Dependencies.scala#L5). A separate module needs to be added & published for Junit 5 support.
It might turn out not so easy to select this version dynamically from HOCON... to be researched
`org.virtuslab.ideprobe.IntelliJFixture#startIntelliJ` has `Runtime.getRuntime.addShutdownHook(new Thread(() => runningIde.shutdown()))`, so theoretically the IDE should always get killed... but I observe that IDEs accumulate from Gradle runs that's been killed with Ctrl+C 🤔
Asked by @pawelprazak : How difficult would it be to generate a DSL automatically based on OpenAPI (see `iat-openapi` sbt module)? https://github.com/fkorotkov/k8s-kotlin-dsl#complete-deployment-example
As for now, e.g. `upsert` methods are side-effecting but paren-less (other than implicit param list), this goes against the Scala conventions
Unless there's a specific need to use the former... but I don't think there is
@pawelprazak : possibly the piece for custom resources as seen here: https://github.com/amir/cr4s/blob/master/example/src/main/scala/Foo.scala could be used