[
https://issues.jboss.org/browse/JBDS-2048?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-2048:
-------------------------------------
Just hit the same problem fixing JBIDE-10244. I think that pathc is fixes only FAIL2, but
not FAIL1.
There are two different activities mixed in one here. I believe in "dirty"
runtime plugin the flow was:
1. Configure EAP included into installation without asking about it;
2. Configure locations for scanning and start scanner (that should show dialog if at least
one runtime is discovered)
Now it just gets locations configured during installation form properties file, adds
location for EAP if it is installed and configures all found runtimes without asking.
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