[jbosstools-issues] [JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026314#comment-13026314 ] 

Martin Malina commented on JBIDE-13445:
---------------------------------------

Unfortunately it does not work in JBDS 8.0.1.CR1 B352. I think we just got confused: I said that perhaps this was superseeded by JBIDE-17180 . But in that JIRA I was mainly concerned about the UI being properly adapted for the different use cases, so when I said it was finally ok except for the wrong warning, I didn't actually check if the custom deployment scanner is added.

Anyway, instead of reopening JIRA and making it longer and harder to read, I created a new JIRA: JBIDE-18912

> Enable possibility of deployment scanner additions for remote servers
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-13445
>                 URL: https://issues.jboss.org/browse/JBIDE-13445
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: server
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.2.1.CR1
>
>
> Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc.  There is a lack of api here, and that will need to be fixed before this issue can work.
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. 



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)