[
https://issues.jboss.org/browse/JBDS-2048?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-2048:
-------------------------------------
Just hit the same problem fixing JBIDE-10244. I think that pathc is
fixes only FAIL2, but not FAIL1.
In my previous comment I have mentioned that FAIL1 isn't fixed and explained why I
didn't fix it.
Only if the installer explicitly added a specific named server do we
do autosetup.
Right. FAIL1 is related to the runtimes the user added when executed the JBDS installer.
They are created automatically without showing the dialog.
This dialog can be easily added. IMO, it is unnecessary because it is certain that the
user wants to create runtimes that he added when installing JBDS.
The fix for FAIL2 has been committed to the trunk only.
Runtime detection: Location not added to the paths list
-------------------------------------------------------
Key: JBDS-2048
URL:
https://issues.jboss.org/browse/JBDS-2048
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: runtime
Affects Versions: 5.0.0.Beta1
Environment: Mac OS X 10.7 Lion latest
jbdevstudio-product-universal-5.0.0.v201203010100M-H88-Beta1.jar
Reporter: Martin Malina
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 5.0.0.Beta1
Attachments: jbds-2048.patch
Runtime detection for locations added during installation doesn't work correctly.
Scenario:
1. Run JBDS universal installer
2. During installation add two runtime locations: One to be checked at every start, one
not
3. Start the newly installed JBDS with a new workspace
4. Both locations will be searched and servers added without asking the user - FAIL1
5. Go to Preferences -> JBoss Tools -> JBoss Tools Runtime Detection - none of the
locations will be in the list - FAIL2
--
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