4:03 a.m.
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, 5.0.0.M2
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:13 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1673:
-------------------------------------------
Consequences of B:
The installer will not show or ask what servers will be setup - that will happen on every
new workspace startup instead (or more specifically on every workspace that doesn't
have been using runtime detection before).
Runtime detection will ask for every server found that is not yet setup and you as a user
can say yes/no to get it installed.
One danger is users pointing to very large directories - not sure how we can avoid or
reduce that problem.
The advantages of this approach is the installer gets simpler, it is not out of sync and
when there are updates to the detection plugins they will pick up new servers where is
before it was just done by the installer which should optimally only be run *once*
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.M2, 5.0.0.M3
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:15 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1673:
-------------------------------------------
Note: A would keep duplication but be more exact since it persist there specific
configurations. But i'm not really sure that is worth the duplicated UI and workflow?
Thus i'm most for B as it stands.
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.M2, 5.0.0.M3
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-1673:
-------------------------------------
We discussed option B as an option to fix UI and code duplication with Lukash,
I'm for option B.
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.M2, 5.0.0.M3
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:24 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1673:
-------------------------------------
I'm for option B.
+1
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.M2, 5.0.0.M3
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:26 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-1673:
--------------------------------------
Fix Version/s: (was: 5.0.0.M2)
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
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:56 p.m.
New subject: [JBoss JIRA] Work started: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Work on JBDS-1673 started by Denis Golovin.
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
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:47 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Denis Golovin edited comment on JBDS-1673 at 7/22/11 6:45 PM:
--------------------------------------------------------------
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 ?
*Consequences of B:*
The installer will not show or ask what servers will be setup - that will happen on every
new workspace startup instead (or more specifically on every workspace that doesn't
have been using runtime detection before).
Runtime detection will ask for every server found that is not yet setup and you as a user
can say yes/no to get it installed.
One danger is users pointing to very large directories - not sure how we can avoid or
reduce that problem.
The advantages of this approach is the installer gets simpler, it is not out of sync and
when there are updates to the detection plugins they will pick up new servers where is
before it was just done by the installer which should optimally only be run *once*
was (Author: maxandersen):
Consequences of B:
The installer will not show or ask what servers will be setup - that will happen on every
new workspace startup instead (or more specifically on every workspace that doesn't
have been using runtime detection before).
Runtime detection will ask for every server found that is not yet setup and you as a user
can say yes/no to get it installed.
One danger is users pointing to very large directories - not sure how we can avoid or
reduce that problem.
The advantages of this approach is the installer gets simpler, it is not out of sync and
when there are updates to the detection plugins they will pick up new servers where is
before it was just done by the installer which should optimally only be run *once*
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
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Denis Golovin updated JBDS-1673:
--------------------------------
Attachment: screenshot99.png
screenshot98.png
screenshot97.png
screenshot96.png
screenshot95.png
screenshot94.png
screenshot93.png
screenshot90.png
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.
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 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
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
6:29 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
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 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!
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.
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!
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 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
6:36 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Denis Golovin resolved JBDS-1673.
---------------------------------
Labels: new_and_noteworthy (was: )
Release Notes Text: 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.
Resolution: Done
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
Labels: new_and_noteworthy
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 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
5:02 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1673:
-------------------------------------------
Looking at the new screenshots - Feels like one page/version is missing ? the case where a
server is already installed ?
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
Labels: new_and_noteworthy
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 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
12:19 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Denis Golovin updated JBDS-1673:
--------------------------------
Attachment: screenshot100.png
I forgot to mention this case, here is a screenshot for this page for installer with EAP
included.
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
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 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 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
12:21 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
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 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!
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.
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 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!
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
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
6:16 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
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
10:42 a.m.
New subject: [JBoss JIRA] Closed: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Pavol Srna closed JBDS-1673.
----------------------------
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
10:42 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Pavol Srna commented on JBDS-1673:
----------------------------------
Verified on jbdevstudio-product-linux-gtk-5.0.0.v201109071858R-H28-M3.
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
10:49 p.m.
New subject: [JBoss JIRA] (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Isaac Rooskov updated JBDS-1673:
--------------------------------
Release Notes Docs Status: Documented as Feature Request (was: Needs More Info)
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:49 p.m.
New subject: [JBoss JIRA] (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Isaac Rooskov reopened JBDS-1673:
---------------------------------
correcting release note status
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:49 p.m.
New subject: [JBoss JIRA] (JBDS-1673) Installer should align with runtime detection
[
https://issues.jboss.org/browse/JBDS-1673?page=com.atlassian.jira.plugin....
]
Isaac Rooskov closed JBDS-1673.
-------------------------------
Resolution: Done
Reclosing issue
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4403
days inactive
4739
days old
jbosstools-issues@lists.jboss.org
20 comments
5 participants
participants (5)
-
Denis Golovin (JIRA) -
Isaac Rooskov (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Pavol Srna (JIRA)
-
Snjezana Peco (JIRA)