[GRADLE-3539] NullPointerException from gradle --status or gradle --stop on Solaris Created: 29/Aug/16 Updated: 07/Sep/16 Resolved: 07/Sep/16
|Reporter:||Eric Wendelin||Assignee:||Jendrik Johannes (Inactive)|
OS is Solaris 10. Started breaking after 2.12, probably in 3.0.
Seems like non-build commands sent to Daemon result in NPE.
|Comment by Jendrik Johannes (Inactive) [ 06/Sep/16 ]|
@wolf and me investigated the exception stack traces.
Looks like this is caused by an automatic unboxing of
in DefaultDaemonContext. It looks like it is only happening in exception handling cases where PID is a primitive long (DaemonStopEvent and Status). If null is valid value for PID (which seems to be the case) it Long should probably be used everywhere.