Extend CONTRIBUTING.md and adapt some Eclipse project settings to simplify getting started#176
Extend CONTRIBUTING.md and adapt some Eclipse project settings to simplify getting started#176travkin79 wants to merge 3 commits into
Conversation
|
Hello @jdneo, Besides, I had some questions left:
|
Describe how to import projects and how to run them in Eclipse
Make all projects importable via File > Import... > General > Existing Projects into Workspace, no need to use the Maven project import wizard.
a335576 to
0f40d70
Compare
|
Thank you, sorry for the confusion we have. I guess we do have some gaps here for the contribution.
This is a good point. TBH, I usually just using the running platform to makes sure the launched debug session is similar to a real eclipse instance. But when it comes to debug a test case, I will switch to target-terminal.target because I use a newer Eclipse version. (There is a bundle namespace change between old eclipse and new eclipse for the terminal bundle, that's why we have two of them.) But I admit that this setup is wired, I'm just not able to find some time organize them systematically.
Because I usually use running platform as the target platform, so when I launch a debug session, I enabled all the plugins. Maybe this is not the best practice? Any suggestions? |
This PR
.projectfiles and Eclipse settings to simplify Eclipse project import for new developers