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

[Isaac Rooskov (JIRA)]

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

Isaac Rooskov updated JBDS-1673:
--------------------------------

    Release Notes Docs Status: Needs More Info
                       Writer: irooskov
           Release Notes Text: The JBoss Developer Studio installer server detection did not allign with runtime detection from within the tooling. When detection plug-ins were updated, new servers were not automatically detected due to the code split between detection through the product installation wizard and runtime detection within the user interface. In this release, on first start-up, the installer asks for a list of directories to scan for new servers. The directory selected will then be optionally scanned on every subsequent launch of the JBoss Developer Studio and new discovered servers will be displayed in a list to the user. This allows for new servers to be detected, while not having to duplicate the code and combine it with the runtime detection available from within JBoss Developer Studio.   (was: Installer's step 5th changed. Instead of detecting servers it now lets to configure locations what Runtime Detection farmework will scan to detect Platforms, Servers and Runtimes like Seam/Drools.)


Updated Release Notes field text - awaiting confirmation from developer

> 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
>      Security Level: Public(Everyone can see) 
>          Components: installer
>            Reporter: Max Rydahl Andersen
>            Assignee: Denis Golovin
>            Priority: Blocker
>              Labels: new_and_noteworthy
>             Fix For: 5.0.0.M3
>
>         Attachments: screenshot100.png, 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 for version w/o EAP to look like 
> !screenshot90.png!
> for version w/ EAP 
> !screenshot100.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 JBDS-1795
> !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