You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bndtoo...@googlegroups.com
Hi team,
I pray that you are well.
It seems my WIP for the JUnit stuff has broken the Gradle plugin tests. I might have to roll up my sleeves and dig in here to figure out what I've done.
I was wondering what IDE tools people are using for developing/testing the Gradle plugin? Eclipse+GDT? Eclipse+Bnd Gradle plugin itself? Jspresso for Spock integration?
I'm sure I can muddle through and figure out something, but if someone could spare a few words and give me a leg-up so I can save some time (of which I seem to be running severely short these days) that would be much appreciated.
Blessings,
Fr Jeremy
BJ Hargrave
unread,
Jun 21, 2019, 9:13:02 AM6/21/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bndtoo...@googlegroups.com
I do all the gradle plugin development. I have never tried to hook a
debugger up to the gradle test case. I am not sure what would be
useful since all our code is in groovy. I normally just don't make
mistakes :-) Actually I use debug logging to help and review the test
output from the gradle runner.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bndtoo...@googlegroups.com
Heh, no problem. If you have a look at the source for my JUnit PR you'll see I'm quite the fan of debug-by-System.err.println() myself. :)
I managed to figure out by running the Gradle test from the command line Roth debugging on that the hanging test is because the tester bundle doesn't resolve, and the test relies upon the tester bundle to call System.exit() for it to end. Should be able to fix in the next couple of days.