Christopher Dieringer
Christopher Dieringer
> does this mean that the trouble you faced is resolved in your case? Yep! > honestly appreciate the persistence ... since #437 ya no problem. > what i'm not...
Awesome, ya let's close!
i rolled back from gradle 3.0 to 2.12 and it worked ok.
nevermind, it re-surfaced today :( there's some nuance in the system. i'll see if i can't isolate it, but this is real bummery!
@akhikhl, is there any further information to provide that would aid in determining root cause here? i'm not familiar with developing gradle plugins and running them locally such that I...
a co-worker had me hack the following in: `````` gradle dependencies { classpath 'org.akhikhl.gretty:gretty:1.4.0' + classpath 'org.akhikhl.gretty:gretty-runner:1.4.0' } `` ```gradle ... compile project(':core') + grettyRunnerJetty7 'org.akhikhl.gretty:gretty-runner:1.4.0' } `````` it works,...
Implicitly asked for is for the extension to (possibly build), resolve, and evaluate code so it could deduce the test name, such that the plugin could give a solid match...
> Would parsing with a regex be too complex? explain more! what's discussed above is a test name discovered by runtime evaluation _of_ the test runner or node.js
Option 2. Give the opportunity to implementations that need max performance the ability to achieve max performance.
I think that this is supposed to happen based on seeing some demos, but my current execution line does not show up either, nor does the viewport scroll with execution....