[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection

[Denis Golovin (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Golovin updated JBDS-1673:
--------------------------------

    Description: 
The installer currently has its own form of server detection which generates a file that runtime detection uses to configure specified servers.
The detection code is not shared and the workflow/power of them are different.

After discussion option B) is selected.

Implementation details.

1. Runtime detection startup is modified to check list of paths in ${target}/studio/runtime_locations.properties generated by installer (I made it this way because there is no way to reuse preferences generation from installer).
2. Installer's step 5 is modified to look like 
!screenshot90.png!
It lets to add new location
!screenshot93.png!
Edit new location
!screenshot95.png!
remove new loaction or locations,
change "Scan every start" in list without opening dialog
!screenshot94.png!
3. After start it shows Runtime detection dialog with discovered runtimes in locations configured in installer
!screenshot96.png!
which is blocked by modal usage dialog JBIDE-????
!screenshot97.png!
4. Preferences contains list of locations added in installer
!screenshot98.png!
5. Discovered and selected servers are created in Servers view
!screenshot99.png!


  was:
The installer currently has its own form of server detection which generates a file that runtime detection uses to configure specified servers.

The detection code is not shared and the workflow/power of them are different.

I suggest we either:

A) extract the detection code and uses that in both places

OR

B) change the installer to just ask for directories to scan on every startup which then needs
somehow to be read by the runtime detection and then it takes over all this

WDYT ?







> Installer should align with runtime detection
> ---------------------------------------------
>
>                 Key: JBDS-1673
>                 URL: https://issues.jboss.org/browse/JBDS-1673
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: installer
>            Reporter: Max Rydahl Andersen
>            Assignee: Denis Golovin
>            Priority: Blocker
>             Fix For: 5.0.0.M3
>
>         Attachments: screenshot90.png, screenshot93.png, screenshot94.png, screenshot95.png, screenshot96.png, screenshot97.png, screenshot98.png, screenshot99.png
>
>
> The installer currently has its own form of server detection which generates a file that runtime detection uses to configure specified servers.
> The detection code is not shared and the workflow/power of them are different.
> After discussion option B) is selected.
> Implementation details.
> 1. Runtime detection startup is modified to check list of paths in ${target}/studio/runtime_locations.properties generated by installer (I made it this way because there is no way to reuse preferences generation from installer).
> 2. Installer's step 5 is modified to look like 
> !screenshot90.png!
> It lets to add new location
> !screenshot93.png!
> Edit new location
> !screenshot95.png!
> remove new loaction or locations,
> change "Scan every start" in list without opening dialog
> !screenshot94.png!
> 3. After start it shows Runtime detection dialog with discovered runtimes in locations configured in installer
> !screenshot96.png!
> which is blocked by modal usage dialog JBIDE-????
> !screenshot97.png!
> 4. Preferences contains list of locations added in installer
> !screenshot98.png!
> 5. Discovered and selected servers are created in Servers view
> !screenshot99.png!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira