OSEE/Developer Setup

Initial Setup

1. Create a UserData Folder on your C: Drive - C:\UserData
2. Install Programs
   1. Google Chrome
   2. Java JDK
   3. DBeaver
   4. Notepad++
3. Create an Eclipse account using your email address
   1. Sign Eclipse Contributor Agreement by going to View Profile then under Status select Eclipse Contributor Agreement
4. Code Reviews - the following links provide access to review code, add links to your browser favorites
   1. Read Gerrit Tutorial
   2. Bookmark and log into: Gerrit at Eclipse.org using eclipse.org un/pw.
   3. When reviewing code, use the Developer Peer Review Checklist
5. Install OSEE Applications
   1. Install OSEE Release
   2. Install OSEE Next Release Beta
   3. Install OSEE Development Alpha
      • Click on SDC -> Alpha Versions (under Groups) -> OSEE Development Alpha
   4. Launch the OSEE Release through Windows start menu. Switch to OSEE Perspective and ensure that your name shows in OSEE Navigator at bottom, if not talk to Mentor
6. Email (Donald Dunne) donald.g.dunne@boeing.com to add you as an OSEE Admin
7. Log into Bugzilla using Eclipse username/password
8. Sign-up to osee-developers mailing list

Git Setup

1. Install Git using the following settings
   • Adjusting your PATH environment
     • Use git from the windows command prompt
   • Choosing HTTPS transport backend
     • Use the OpenSSL library
   • Configuring the line ending conversions
     • Check as-is, commit as-is
   • Configuring the terminal emulator to use with Git Bash
     • Use MinTTY
   • Leave the rest of the settings as default

• Rest of the Git Setup is TBD

OSEE Workspace Setup - For when Git Repo Setup is Complete

Importing Git Projects

1. Start an OSEE version that matches the code you want to develop (e.g. dev alpha to develop in dev)
2. Create a workspace
3. In OSEE, follow the menu Project->Build Automatically, and uncheck this option
4. Open the Git Perspective by following the menu Window->Perspective->Open Perspective
5. Click the first "GIT" icon labeled, Add an existing local Git Repository
6. Browse to select the git directory (created in a previous section above, e.g. C:\UserData\git_main), then click Search
7. In the Search and select Git repositories on your local file system dialog, (choose available repos, TBD)
8. Click the Finish button
   • For each of the repositories, Right-Click on the repository now showing in the Git Repositories view and select Import Projects...
   • In the dialog that pops up, take the default Import existing Eclipse projects, select the Next button
   • After the import take a quick look to make sure all projects are selected, then choose Finish
   • Don't forget to complete these steps for all repositories

Configure Workspace

1. Double check to make sure the OSEE environment you are pulling code into matches the code you have.
   • e.g. if you are developing for the dev line, make sure your osee is a dev version.
2. Import OSEE Team Preferences
   • Switch back to the Java Perspective, then File->Import, in the import wizard, select General->Preferences
   • In the From preference file: input box, enter the path to the preferences (substitute your directory for <git dir>) in the From preference file:
   • Browse to <git dir>\org.eclipse.osee\plugins\org.eclipse.osee.support.config then select the preference file: osee_team_preferences.epf
   • Choose Finish
3. Set Target Platform
4. Turn Project->Build Automatically back on
5. Remove errors that we do not care about
   • In the Problems tab at the bottom of OSEE, select the white triangle icon on the right side
   • Choose Configure Contents
   • Uncheck Show all items
   • Choose New under Configurations
   • Deselect All Errors, then make sure New Configuration is both selected and highlighted
   • In the Types box on the bottom right, de-select Xtext checks, Xtend Problems, DisplayLogic DSL problems, and MWE2 Problem
6. Remove Null Analysis Errors
   • Choose Window->Preferences->Java->Compiler->Errors/Warnings
   • Expand Null Analysis and set the following to Warning instead of Error
   • Null pointer access
   • Potential null pointer access
   • Redundant null check
   • Uncheck Enable annotation-based null analysis
   • Click Apply then Ok
   • There should no longer be any errors, otherwise ask Mentor

Other OSEE Settings

• Package Explorer > White Pull down Arrow > Package Presentation > Change to Hierarchical from Flat (if preferred)

OSEE Setup Checks

1. Ensure that engineer's name shows in OSEE Navigator when they launch
2. User added as assignee in Backlog
3. User understands the Backlog, My World, New Actions, Actionable Items, Target Definitions, Versions
4. Run Test Suites / DB Init
   1. Under Debug Configurations, OSGi Framework, run "OSEE_Application_Server[HSQLDB]"
   2. Once server is loaded, go to Debug Configurations, JUnit Plug-in Test, run "AtsIde_Integration_TestSuite"
   3. Once ~100 tests have loaded and passed in JUnit, stop the tests, terminate and relaunch the Application Server
   4. Run "OSEE_IDE_[localhost]" under Eclipse Application in Debug Configurations
   5. OSEE IDE should load without issue

Maven Setup TBD

Other Programs & System Configuration

• Wiki for Documentation
  • Bookmark and log into Eclipse.org Wiki
  • Bookmark and log into MSA Wiki
• Log in and bookmark Jenkins Build Page

Reading & Training Material

• TBD What is goes here