Dear all,
I would like to ask your wisdom. I would like to trace the calls to the
Gradle project loading infrastructure, as some reloads are happening
without a reason (at least for me). So in the Gradle project loading I
would like to know 3 things: The original caller thread name if
possible, the callstack and a reason message.
For the purpose it seems to be good to create a custom Exception type
and pass instances of it as a parameter through the call chain. So at
the point of loading I can print some nice debug messages. Though these
custom exceptions are not meant to be thrown or to be caught.
Could this be a valid use case to use Exceptions for such purpose?
--
Laszlo Kishalmi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
