erlide not compiling with eclipse - eclipse

I am able to run my code using my installation of erlang, but I want to integrate it into eclipse. I am having problems setting up the run configurations. Below are screenshots of how I have the run configuration configured.
http://imgur.com/a/CSBNg
The specific error message is:
An internal error occurred during: "Launching HelloWorldProject".
Expected the service to be RUNNING, but the service has FAILED

'erlide' as a name for the Erlang node is reserved (used by Erlide itself). Try another. I will add a check for that and show a better error message.

Related

Running an Erlang Application in Eclipse is throwing an exception

I have installed Erlang OTP 25.0, erlide 0.56.0, Eclipse 2022-09 & Java 18. I have created a new Erlang project and module. I am facing 2 issues.
Issue #1:
Getting an error when I tried to launch the Eclipse after creating the Erlang project.
Issue #2:
When I tried to run the application, I am getting an exception "Launching App1 has encountered a problem. An internal error occurred during launching App1. Expected the service OtpNodeProxy 5756dc#null FAILED to be running, but the service has FAILED" as shown in the screenshot ErlangRunConfigException. Please help me in resolving the issue.
I have followed the procedure given below.
Installed Eclipse and Erlide plugin
Installed Erlang OTP 25.0 from https://www.erlang.org/patches/otp-25.0
Updated the environment PATH to refer to the Erlang installation path. I cross-checked this setting by typing "werl".
In Eclipse, Erlang InstalledRuntimes is automatically updated with the Erlang version 25.0. Refer to the screenshot ErlangInstalledRuntime
Created a Erlang project and module.
Edited the Hello.erl with HelloWorld code.
In Eclipse->RunConfguration, created an ErlangApplication (refer to the screenshot RunConfig-ErlangApp-Erlang). I set RunTime and Node name as shown in the screenshot RunConfig-ErlangApp-Runtime. Selected the Windows PATH as shown in the screenshot RunConfig-ErlangApp-Environment.
Hello.erl
```
-module(hello).
-export([hello_world/0]).
hello_world() -> io:fwrite("hello, world\n").
```
Images:
ErlangRunConfigException.png
ErlangInstalledRuntime.png
RunConfig-ErlangApp-Environment.png
RunConfig-ErlangApp-Runtime.png
werl output
RunConfig-ErlangApp-Erlang.png
Project structure
Eclipse Launching Error
Unfortunately, Erlang 25 doesn't load beam files older than v21, and the files included in erlide are that old. I am not really maintaining the project anymore, I can try to rebuild with v25, but can make no promises. Even then, the debugger will no longer work, it can be good to note.
The reported issue is seen with the latest Erlang version 25.0 and the older versions I have checked till 23.0. As a workaround, I have migrated to IntelliJ IDE.

Eclipse Maven debug - source not found

I am trying to debug a JUnit test case within a Maven project in Eclipse on my local machine and I am getting a "Source not found" error on my own test class. I went through all the other similar threads that I could find about the problem, but to the best of my understanding none of them addresses exactly my same problem, nor a solution for it. So here is the detail of what I have done:
Created a run configuration with the goals "-Dmaven.surefire.debug -Dtest=MyTestClass test"
Created a remote Java application that connects to localhost:5005. Added the base folder for the project in the "Source" tab.
Setup a breakpoint in MyTestMethod in MyTestClass. MyTestMethod has the #Test tag.
Run the run configuration in 1. The application stops listening on port 5005.
Debug the remote Java application in 2. The debugger window pops up and I see the thread with the stack trace of the classes where things are stopped. The debugger is stopped at the breakpoint that I setup. I can see the variables in this class and in other classes as well, but I get "Source not found" for MyTestClass. If I do "Edit source lookup path", my project is there as I added it in 2.
I am not sure what I am doing wrong. As an alternative, I have also tried to create another run configuration with -DforkMode=never. But if I try to debug that, I get the following error:
ERROR context.TestContextManager: Caught exception while allowing TestExecutionListener
[org.springframework.test.context.support.DependencyInjectionTestExecutionListener#2a46b75b]
to prepare test instance [MyTestClass#8afcd0c]
Thanks.

Error has eccurred in Eclipse during importing class

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.

Oracle WebLogic Server is "Stopped" and yet I can't start it in Eclipse

When I open the Servers view in Eclipse (Galileo), I have a localhost instance of WLS with a "[Stopped]" indicator on it. When I attempt to start the supposedly stopped instance, I get these errors:
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
The "Address already in use" part clued me in that WLS was already running.
How can I stop/view the output of the currently running instance?
I normally run WLS through the command line (Windows) separately but I'm starting to fiddle around with running WLS right inside of Eclipse.
I've been searching for a good guide on setting Eclipse up to interact with WLS but haven't found one yet. If any of you can recommend one I would appreciate that as well.
the message you see means that java debugger cannot bind to the specified port, and not (yet) that weblogic cannot bind to its listen address.
This, can be due to an existing running weblogic instance (running with debugger enabled and on the same port) as you say, but may also mean that another Java program has been started with JDWP enabled on the same port.
So in the second case, please search if there is such a process (netstat -a will help) or just change debugger port you are trying to start weblogic with
If instead you really have a running weblogic instance, there are three cases:
1) it is a windows service (strange that you run weblogic as a service with JDWP activated), thus you can search and stop it through windows services ui
2) you started it through the command line, but in this case you would easily find the command line window you used to start it.
3) it is started by eclipse and you cannot see it for any reason, which is quite strange since it means that eclipse would have started two weblogic instances and one is failing. You can search in eclipse console view if you find a running instance (many consoles can be used at the same time). IF you don't find it just try to quit eclipse, WLS must die together with eclipse and you will see it in weblogic logs or through WLS process disappearing from task manager.
Are you using Oracle Enterprise Pack for Eclipse for running weblogic there? If yes I think this is a good introduction:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/jdev/obe11jdev/11/oepe11g/introeclipseide.htm

Headless build in Eclipse: how to retrieve result value

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