Skip to content

Extend CONTRIBUTING.md and adapt some Eclipse project settings to simplify getting started#176

Draft
travkin79 wants to merge 3 commits into
microsoft:mainfrom
travkin79:patch/update-contribution-guide
Draft

Extend CONTRIBUTING.md and adapt some Eclipse project settings to simplify getting started#176
travkin79 wants to merge 3 commits into
microsoft:mainfrom
travkin79:patch/update-contribution-guide

Conversation

@travkin79
Copy link
Copy Markdown

@travkin79 travkin79 commented May 12, 2026

This PR

  • explains in more details how to start contributing, e.g. how to import Eclipse projects and how to launch the plug-ins
  • adds .project files and Eclipse settings to simplify Eclipse project import for new developers
  • Explains how to configure the Checkstyle Eclipse plug-in to work with this git repo

@travkin79
Copy link
Copy Markdown
Author

Hello @jdneo,
I have some suggestions how to simplify the first steps for new contributors. Could you please take a look at this PR? Do the suggestions make sense for you? Is it ok to have them in one single PR?

Besides, I had some questions left:

  • Which of the two target definition files are you usually using for development? I took target-tm-terminal.target
  • It seems, the launch config launch/plugin_debug_configuration.launch is not up-to-date or incomplete. For example, I didn't see any agent bundles selected. Are you usually using some other launch config? I guess, there should be different launch configs, one for each OS or one config explicitly for a particular OS.

travkin79 added 3 commits May 12, 2026 12:54
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.
@jdneo
Copy link
Copy Markdown
Member

jdneo commented May 12, 2026

Thank you, sorry for the confusion we have. I guess we do have some gaps here for the contribution.

Which of the two target definition files are you usually using for development? I took target-tm-terminal.target

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.

It seems, the launch config launch/plugin_debug_configuration.launch is not up-to-date or incomplete. For example, I didn't see any agent bundles selected. Are you usually using some other launch config? I guess, there should be different launch configs, one for each OS or one config explicitly for a particular OS.

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants