[
https://issues.jboss.org/browse/JBIDE-14584?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-14584.
---------------------------------
Resolution: Done
The proper api would be:
IRuntimeDetector rtdet = RuntimeCoreActivator.findRuntimeDetector(String id);
IRuntimeDetectorDelegate del = ((RuntimeDetector)rtdet).getDelegate();
This api is not new, we just didn't see it earlier.
Runtime Detection needs API for finding runtime detectors by ID.
-----------------------------------------------------------------
Key: JBIDE-14584
URL:
https://issues.jboss.org/browse/JBIDE-14584
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: runtime-detection, server
Affects Versions: 4.1.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Beta2
Related to:
https://issues.jboss.org/browse/JBIDE-14559
Test case in central is using internal ASTools API. Long-standing practice is that
extension point id's are api and cannot be changed, but location can. If an id is api,
then a method to search by ID becomes a requirement.
Runtime detection needs apis to find a handler by ID.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira