- This topic has 8 replies, 3 voices, and was last updated 15 years, 3 months ago by
.
-
Posts
-
I am using MyEclipse 7.5. I have created a simple Maven-based java application, including a class with a main method and about 4 other classes.
I successfully use the Maven exec:java plugin/goal to run the application.
However, when running in debug mode, as soon as I hit a breakpoint in the code, a “Source not found” dialog appears, including an “Edit Source Lookup Path …” button. I click the button and, in the dialog that is displayed, I “Add” the project of the very code I am debugging, and the relevant code is presented and I can step through it with no problems.
However, the problem I have is that I have to go through this same process (of editing source lookup path, ect.) EVERY time I go into debug mode.
Is there any way of configuring things so that I don’t have to keep repeating this?
Thanks,
knarfsnrub
knarfsnrub,
What server are you working with? Are you working with weblogic ? Can you try the following steps:-
1. Create a Launch Configuration for WebLogic by going to Window > Prefs >MyEclipse > App Servers > WebLogic > <Vesion you are using> > Launch, click the button.
2. Hit Apply/OK
3. Go to the Run menu, then Open Run Dialog
4. Find your Run Configuration for WebLogic. Go to the Source tab, click Add, add all your projects to it and hit OK.
5. Now use this run Configuration to start/stop WebLogic.Does this help?
I’m not using a server. It’s a straightforward java application (kicked off from a main() method via a Run Configuration in Eclipse using the Maven exec:java plugin/goal).
The problem is being able to view the code from MY application (not of a Maven dependency).
Thanks,
knarfsnrub
Unfortunately, we haven’t considered this scenario. Can you run your application as plain Java application? The debugger should work fine then. I will open a problem report on your scenario.
Your answer has made me curious.
You say that you haven’t considered this scenario. But isn’t what I am trying to achieve THE simplest scenario, i.e., run the debugger on a Maven-based java application?
Perhaps my approach is wrong. Should I be using something else (other than the Maven exec:java plugin/goal) to run the app via Maven within Eclipse? Is there another way to run and debug an app, whilst staying within the Maven umbrella within Eclipse?
Thanks,
knarfsnrub
MyEclipse support for Maven is designed to allow building MyEclipse projects outside MyEclipse IDE – i.e. on dedicated build machine or other IDE. We plan to broaden this support in the next MyEclipse versions.
