Summary: | Connection "Local" always created on startup even if another local connection exists | ||
---|---|---|---|
Product: | [Tools] Target Management | Reporter: | Kevin Doyle <kjdoyle> |
Component: | RSE | Assignee: | David McKnight <dmcknigh> |
Status: | CLOSED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> |
Severity: | trivial | ||
Priority: | P5 | CC: | dmcknigh, kmunir |
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: | |||
Bug Depends on: | 196838 | ||
Bug Blocks: |
Description
Kevin Doyle
2007-06-19 10:37:01 EDT
This should be simple to fix (I think there is SystemRegistry.getLocalConnection() or something like that which would need to be updated), but I'm not sure if we really want to fix it since it appears to be really low in priority. I dont think that any extenders can expect the connection named "Local" to always be there, so either case I don't see this as a big issue. Fixed through the fix for bug #196838 Verified with driver I20070719-1300. |