It's not about deprecating an API. It's about to encourage people to take care of their build scripts, in order not to rely on our heuristics. Also the way IDE actions mapped to build system calls can be configured in project properties Build > Build Actions
My brain is probably scrambled here, so could you give me a hint how to do that? Currently the IDE action "Run File" is mapped to:
-PrunClassName=${selectedClass} ${javaExec.workingDir} ${javaExec.environment} runSingle --stacktrace ${javaExec.jvmArgs} ${javaExec.args}
If this is not a gradlew command-line, but some proprietary syntax, then how do I need to translate that into Gradle syntax? And how would my task "runSingle" then have to look?
I suppose I need to replicate what the Build Augmentation does? And somehow do a better job than the heuristic? :)
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
