Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "JDT Code Setup Using Oomph"

(Commonly used Preference setup)
(added note linking to Eclipse_Platform_SDK_Provisioning)
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This page is a work in progress ...<br>
+
This page is a simple starting point for where to begin when wanting to contribute to the JDT project using Oomph. The goal of this wiki page is to help users to set up coding workspace for JDT components using Oomph.
This page is a starting point for where to begin when wanting to contribute to the JDT project using Oomph. The goal of this wiki page is to help users to setup coding workspace for JDT components using Oomph.
+
 
 +
{{Note|Note|There is also a more comprehensive page [[Eclipse_Platform_SDK_Provisioning]], which explains how to pull in even more Eclipse projects and also explains working with Oomph in more detail.}}
  
 
== Setting up Oomph==
 
== Setting up Oomph==
Oomph can be extracted to a local folder after downloading it from https://wiki.eclipse.org/Setup-Eclipse.<br>
+
Oomph can be extracted to a local folder after downloading it from [[Eclipse Installer]] (by Oomph).<br>
You can know more about Oomph project at https://projects.eclipse.org/proposals/oomph
+
You can learn more about the Oomph project at https://projects.eclipse.org/proposals/oomph<br>
FAQ is available at https://wiki.eclipse.org/Eclipse_Oomph_FAQ
+
FAQ is available at [[Eclipse_Oomph_FAQ]]
  
 
== Using Oomph==
 
== Using Oomph==
  
=== Commonly used Preference setup===
+
=== Selecting Advanced Mode===
 +
Code setup using Oomph Installer for Eclipse is available in Advanced mode.<br>
 +
[[File:OomphAdvancedMode.PNG]]
 +
 
 +
=== Commonly used Preferences===
 
Eclipse has many workspace-specific preferences. Oomph helps us set the preferences across all workspaces.<br>
 
Eclipse has many workspace-specific preferences. Oomph helps us set the preferences across all workspaces.<br>
Oomph can manage following preferences and by enabling the last preference, any preference set later can be managed by Oomph:
+
Oomph can manage following preferences and by enabling the last preference (Enable Oomph Preference Recorder), any preference set later can be managed by Oomph:<br>
Refresh Resources Automatically?<br>
+
* Refresh Resources Automatically?<br>
Show Line Numbers in Editors?<br>
+
* Show Line Numbers in Editors?<br>
Check Spelling in Text Editors?<br>
+
* Check Spelling in Text Editors?<br>
Execute Jobs in Background?<br>
+
* Execute Jobs in Background?<br>
Encode Text Files with UTF-8?<br>
+
* Encode Text Files with UTF-8?<br>
Enable Oomph Preference Recorder?<br>
+
* Enable Oomph Preference Recorder?<br>
  
 
=== Eclipse Product and Version selection===
 
=== Eclipse Product and Version selection===
 +
Select Eclipse Product as <B>"Eclipse IDE for Java Developers"</B><br>
 +
Product version can be selected as required.<br><br>
 +
[[File:ProductSelection.PNG]]<br>
  
=== Project setup===
+
=== Project Selection===
 
+
Projects to be selected for components JDT Core, JDT UI and JDT debug: <br><br>
=== Variable setup===
+
[[File:CoreProject.PNG]][[File:UIProject.PNG]][[File:DebugProject.PNG]]
 
+
====Eclipse Install====
+
 
+
====Workspace====
+
 
+
====JDT Core====
+
  
====JDT Core Binaries====
 
  
====JDT UI====
+
=== Variable Selection===
 +
Rules and details for Install, Workspace and JRE can be selected based on user choice. For each project (Core, UI and Debug) Git Feature repository connection method needs to be selected. For Core Project there are 2 repositories( Core and Binaries). User can use Git or Gerrit based on there convenience. User without Commit rights should use HTTPS and with commit rights should use SSH. If they have Gerrit account, they can use  HTTPS(read-write, gerrit). HTTP (read only, anonymous, direct) will be the simplest to use.<br>
 +
For more details refer to Oomph Setup and FAQ page. <br>
  
====JDT Debug====
+
[[Category:JDT]]

Revision as of 07:31, 17 September 2019

This page is a simple starting point for where to begin when wanting to contribute to the JDT project using Oomph. The goal of this wiki page is to help users to set up coding workspace for JDT components using Oomph.

Note.png
Note
There is also a more comprehensive page Eclipse_Platform_SDK_Provisioning, which explains how to pull in even more Eclipse projects and also explains working with Oomph in more detail.


Setting up Oomph

Oomph can be extracted to a local folder after downloading it from Eclipse Installer (by Oomph).
You can learn more about the Oomph project at https://projects.eclipse.org/proposals/oomph
FAQ is available at Eclipse_Oomph_FAQ

Using Oomph

Selecting Advanced Mode

Code setup using Oomph Installer for Eclipse is available in Advanced mode.
OomphAdvancedMode.PNG

Commonly used Preferences

Eclipse has many workspace-specific preferences. Oomph helps us set the preferences across all workspaces.
Oomph can manage following preferences and by enabling the last preference (Enable Oomph Preference Recorder), any preference set later can be managed by Oomph:

  • Refresh Resources Automatically?
  • Show Line Numbers in Editors?
  • Check Spelling in Text Editors?
  • Execute Jobs in Background?
  • Encode Text Files with UTF-8?
  • Enable Oomph Preference Recorder?

Eclipse Product and Version selection

Select Eclipse Product as "Eclipse IDE for Java Developers"
Product version can be selected as required.

ProductSelection.PNG

Project Selection

Projects to be selected for components JDT Core, JDT UI and JDT debug:

CoreProject.PNGUIProject.PNGDebugProject.PNG


Variable Selection

Rules and details for Install, Workspace and JRE can be selected based on user choice. For each project (Core, UI and Debug) Git Feature repository connection method needs to be selected. For Core Project there are 2 repositories( Core and Binaries). User can use Git or Gerrit based on there convenience. User without Commit rights should use HTTPS and with commit rights should use SSH. If they have Gerrit account, they can use HTTPS(read-write, gerrit). HTTP (read only, anonymous, direct) will be the simplest to use.
For more details refer to Oomph Setup and FAQ page.

Back to the top