Replies: 2 comments
-
As far as I'm aware, the absolute or project root relative path is not available from the stack trace which is printed by Gradle in this case. |
Beta Was this translation helpful? Give feedback.
-
I think you'll need to implement a custom |
Beta Was this translation helpful? Give feedback.
-
Hi,
I'd like to integrate junit into my Emacs development workflow. Emacs provides the functionality to run shell commands and then parse the output of them to populate a jump list and then quickly jump to each of those failures. It relies on the compilation/lint tools encoding the location info of those failures to make it simple to jump to.
For example if I break a java file and run a build with
./gradlew --daemon --parallel test
then I'll get printed:The
path:line-number: error: message
is a format Emacs can recognize so this error is jumpable. Unfortunately the output format of junit is just the java file name with no details about where the file is located so if you just run all tests from the root of the project you've gotta figure out where the directory containing this file is yourself 😞.Is there a way to encode the full
/tmp/tmp.t36cfaG8Yv/list/src/test/java/org/example/list/
prefix before LinkedTest.java. Preferably even just the path from the project root or where I started the test command (./gradlew --daemon --parallel test
) would be sufficient.Beta Was this translation helpful? Give feedback.
All reactions