Spring Tool Suite gives me a cryptic error that also says:
See Error Log for more details
QUESTION: Where can I find the error log of Spring Tool Suite?
Nothing in Eclipse's "Console" view
I launched STS from command line, but nothing special is shown on command line, some debug information but nothing that looks like an error
Related
I have configured eclipse runconfigurations as follows;
at Run configurations-->Arguments
-Djavax.net.debug=ssl,handshake
eclipse runtime.
But still at console im not getting any debug logs.(SSL handshake logs)
Why is that?
I get only my system.print statements in console.
Make sure, to configure it as VM argument, not as Program argument.
I have this error message: "Unable to find the apex source" after running a test in the Winter 16' version of Apex in Eclipse, when the project is located in a Git depository. I mean that the test runs. Even shows, at the end, coverage results but there is no System Debug Log information, neither User Debug Log information and instead of writing the name of the class next to the "green V" signaling that the test passed, nothing is written and when I click on it, I have this error message.
Note that when the project is simply in the Eclipse workspace (not in a Git depository), there is no problem, and there is also System Debug Log and User Debug Log information.
I've tried to configure the test running configuration, but with no success.
Is there anyone who knows how to handle that?
Is there any way to view Salesforce debug logs in eclise ide? I tried to do some preliminary search but couldn't find anything.
You can receive debug log in Eclipse only, if you run apex tests or execute anonymous code from Eclipse. In other cases you can find debug logs in Setup->Logs->Debug or in Developer Console.
I am working on Spring MVC project in Eclipse Juno. I have a few packages with my classes. Once I have used one class in another from different package I have occured this error in pop-up message:
An error has occurred. See error log for more details.
assertion failed:
And there is not nothing more informations. What should I do in Eclipse to prevent such errors?
First read about What is assertion.
And looks like assertions are enabled try to run program after disabling it.
I'm trying to use Eclipse CDT's headlessbuild feature for integrating Eclipse with TeamCity. I use a command line call to build my projects as descriped in this question. If there is a compilation error, a message box pops up saying "Java was started but returned exit code=1". I'd rather not have this message but get the return code so I can process it further in my script. Is there any way to do this?
Thanks!
You can suppress the popup and redirect output to be included with your script:
Add "--launcher.suppressErrors" to your command line arguments for eclipse
The error needs to be tracked down in the GUI from what I can tell, because the headless mode doesn't support very good error reporting from sub-tasks yet.
From there I used output from the GUI-based build to narrow down why my project failed to build.
Sources:
http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg15343.html
http://www.eclipse.org/forums/index.php?t=msg&goto=481938&S=c88d71260a7d130eebdccb8f2e5537f2
http://www.eclipse.org/forums/index.php?t=msg&goto=481938&S=c88d71260a7d130eebdccb8f2e5537f2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209080#c21