>What do you mean ? https://www.jetbrains.com/help/idea/project-security.html#open_first_time
>Maybe you can share this configuration in the document. I think we could even share the configuration via .idea/... file (see https://www.jetbrains.com/help/idea/run-debug-configuration.html#share-configurations ) >Does it make startup faster ? The problem is to keep classes up to date. In other words, something should compile the classes and resolve the dependencies appropriately. If you delegate everything to Gradle, then there's a single source of truth. If you do the compilation via IDE (IDEA or Eclipse), then they might do it slightly differently. I have not explored that, so I can't tell :-/ Then, there's an issue that JMeter expects certain jar layout, so jars must be copied before JMeter launches :( Removing Gradle warnings (easily doable now), and moving to (it would require some work) https://docs.gradle.org/current/userguide/configuration_cache.html should improve the startup time. >Does it allow code reload during debugging ? It works with both debugging and when running NewDriver via "Application -> ..." run configuration. The reload is triggered when you modify a class and build the module via Build -> build module '...' or "right-click on module -> build". In case you wonder, I was able to launch NewDriver as follows: classpath: jmeter.src.dist.main working directory: ...\jmeter\bin (I added bin) Vladimir
