One of the most common support issues we get is this error:
error MSB6006: “java.exe” exited with code 1.
This requires directing the user to create a diagnostic MSBuild log to get the real Java error before we can do anything.
It would be nice if we could better parse Java error messages so we could show them directly to the user instead of the MSB6006. Then they could search for that message instead of searching for the generic MSB6006 which often sends them in the wrong direction since it represents an infinite amount of different cases. Hopefully this would result in more users able to figure out the issue without needing to contact us.
One of the most common support issues we get is this error:
This requires directing the user to create a diagnostic MSBuild log to get the real Java error before we can do anything.
It would be nice if we could better parse Java error messages so we could show them directly to the user instead of the
MSB6006. Then they could search for that message instead of searching for the genericMSB6006which often sends them in the wrong direction since it represents an infinite amount of different cases. Hopefully this would result in more users able to figure out the issue without needing to contact us.