cd1a876f31852d29d3c2b21774f33b2928d4bd6d
wiki/howto/development/super-dev-mode.md
| ... | ... | @@ -32,13 +32,15 @@ To start SDM debugging in Eclipse, do the following: |
| 32 | 32 | |
| 33 | 33 | * Start the backend as you would always do. |
| 34 | 34 | * Start GWT Super Dev Mode by launching "SailingGWT sdm.launch" or "SailingGWT All SDM.launch". |
| 35 | -* Do not Click on the URLs provided in "Development view"! |
|
| 36 | -* Make sure that in the Debug Configuration chrome is the first browser used and not chromium. |
|
| 37 | -* Run "Debug SailingGWT SDM on Chrome.launch" |
|
| 35 | +* Do not Click on the URLs provided in "Development view" (this is not essential for MAC users)! |
|
| 36 | +* Make sure that in the _Debug Configurations..._ => *Launch Browser* tab, you set the correct browser search order: _chrome_ **must** be the first one for the SDBG to work correctly. |
|
| 37 | +* Run "Debug AdminConsole" |
|
| 38 | 38 | * A new instance of Chrome is started and you will see a debug session running in Eclipse |
| 39 | 39 | * Your Eclipse break points will now work in the running debug session. |
| 40 | 40 | * You are free to change the URL or navigate to other pages in the automatically openend browser window (debugging will go on) |
| 41 | 41 | |
| 42 | +You may need to go to *Preferences => General => Web Browser*, and click _New_ to add Chrome. |
|
| 43 | + |
|
| 42 | 44 | ### Noteworthy information & Troubleshooting |
| 43 | 45 | |
| 44 | 46 | If you are faced with an error stating that your Chrome installation isn't found, do the following: |