[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21193: ------------------------------------- I have no idea, Max ;) The API asks a given runtime detector for a "RuntimeDefinition" given some file / folder. The RuntimeDefinition that's returned has a name, version, type, etc. But there's no clear mechanism that links it to a specific runtime detector. So, if there's a given workspace with two runtime detectors, WonkaDetector and JBossDetector, and it's provided two paths (~/wonka, ~/jboss), both will be asked to create a RuntimeDefinition for each path. The wonka detector will return one for wonka, the jboss detector one for jboss. But, it should be noted, there's no 1:1 mapping between the runtime definition type and a given detector. So the jboss detector can return a RuntimeDefinition of type EAP, or type JPP, or type EWP, etc etc. The type is just an identifying string. There's no reference to the detector that instantiated it. Anyway, it's expected that a given detector knows what "types" it made, and handles them. So a wonka detector knows it only creates wonka type runtime definitions, and if its given anything else, it should ignore it. I'm sure changes could be made to AbstractRuntimeDetectorDelegate to add some protected methods and add a constructor to RuntimeDefinition to include the given detector and optimize the behavior... but it's not really a huge priority since every detector knows what types htey create. But it'd definitely make the api nicer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)