Debugging, development and testing of eclipse-platform #845
-
|
Hello, ask for advice, |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 8 replies
-
|
Just get it from here: https://download.eclipse.org/eclipse/updates/4.27-I-builds/ Or use the Eclipse SDK as your IDE where everything you'd need is already installed in that IDE and with the IDE as the target platform (which is the default), generally everything you need is available for your plugin development: https://download.eclipse.org/eclipse/downloads/drops4/S-4.27M1-202301041800/ |
Beta Was this translation helpful? Give feedback.
-
|
First of all, thank you for your patience! |
Beta Was this translation helpful? Give feedback.
-
|
One thing I would suggest is setting up a development environment with all the source code projects of the Eclipse SDK: This is is useful because then you can see how everything works and can search all source code easily. This is the environment that many of the platform developers use to develop the platform... One of the things in this environment is this launch configuration:
This lets you debug launch an Eclipse IDE that uses all the plugins in the workspace, so you can set breakpoints and see how things work. This way you can see how JDT's debugger works so that you can do similar things to extend it... You can do the same setup in your own Eclipse SDK installation containing your own projects. It's also very helpful in general to invoke "Add all plugins..." via the quick search action (magnifying glass):
This ensures that Ctrl-Shift-T can find not only the classes in your workspace but also those available in the target platform, e.g., the debug framework classes that you want to use. |
Beta Was this translation helpful? Give feedback.
-
|
One thing I would suggest is setting up a development environment with all the source code projects of the Eclipse SDK: This is is useful because then you can see how everything works and can search all source code easily. This is the environment that many of the platform developers use to develop the platform... One of the things in this environment is this launch configuration:
This lets you debug launch an Eclipse IDE that uses all the plugins in the workspace, so you can set breakpoints and see how things work. This way you can see how JDT's debugger works so that you can do similar things to extend it... You can do the same setup in your own Eclipse SDK installation containing your own projects. It's also very helpful in general to invoke "Add all plugins..." via the quick search action (magnifying glass):
This ensures that Ctrl-Shift-T can find not only the classes in your workspace but also those available in the target platform, e.g., the debug framework classes that you want to use. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I'm ready for the environment. The source code can be seen in the eclipse-altform debug, but the source code can't be seen in the JDT part, and the breakpoint can't be broken. Is there any good way to import the JDT source code into eclipse (https://github.com/eclipse-jdt)?
|
Beta Was this translation helpful? Give feedback.
-
|
Is there any way to run this source code? ( https://github.com/eclipse-jdt/eclipse.jdt.debug ) |
Beta Was this translation helpful? Give feedback.
-
|
You don't need source projects to set breakpoints. JDT also has an Oomph setup which should do a better job importing project such that there are no errors: |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I have used oomph to import the JDT project. Next, I have two questions: Second: How should this project be used? I want to see debug the code logic? |
Beta Was this translation helpful? Give feedback.
-
|
I would expect the setup to install the 4.27 SDK product:
You appear to have installed into an older IDE so I would suggest installing into a newer IDE certainly 2022-12 4.26 at least... |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much. It's OK. Can you guide me how to run it next? (Run this source code) |
Beta Was this translation helpful? Give feedback.
-
|
I suggest Google "eclipse debug launch ide" and read some of that information. You'll need to create a launch configuration like what I showed in #845 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Coincidentally, hello, after I import the JDT code, the result of running now is the eclipse IDE. Is the JDT plug-in used in my source code or in the eclipse IDE itself? |
Beta Was this translation helpful? Give feedback.
-
|
Your launch configuration's plug-ins tab determine what's in the application that you launch. But default it's all the things in the workspace and all the things in the target platform (where the later by default is all the things in the host IDE); the plugins in the workspace generally override the ones in the target platform. |
Beta Was this translation helpful? Give feedback.
-
|
Nice, I found it. Next, wish me good luck! |
Beta Was this translation helpful? Give feedback.
-
|
The articles provided by @vogella are high quality, e.g., https://www.vogella.com/tutorials/EclipseDebugging/article.html |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thank you very much. I will work hard. Thank you for your reply and wish you a wonderful day |
Beta Was this translation helpful? Give feedback.
Your launch configuration's plug-ins tab determine what's in the application that you launch. But default it's all the things in the workspace and all the things in the target platform (where the later by default is all the things in the host IDE); the plugins in the workspace generally override the ones in the target platform.