[jbosstools-issues] [JBoss JIRA] (JBIDE-22625) Remote server with FS operations: Unable to retrieve a list of remote deployment scanners

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-22625:
---------------------------------------

I wonder how many users actually ever understand the difference between the two modes. So this is similar to local server - even fs operations mode still uses management for some functionality, but with a local server it just works. For a remote server you would need to set up the management port when launching the server.

So I think it should be added to the launch command for remote servers even when fs operations are used.

But this brings another question: Shouldn't we just decide on one of the modes we want to support and remove the other? Does it have much value to have two ways of doing the same thing? I'm not sure, I'm just curious what others think about this.

> Remote server with FS operations: Unable to retrieve a list of remote deployment scanners
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22625
>                 URL: https://issues.jboss.org/browse/JBIDE-22625
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.4.0.Final
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> Previously I reported this as part of JBIDE-22605, but I think it deserves its own issue.
> When I setup a remote EAP 7 server with FS operations and then start it, I always get this in the error log:
> Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0
> Today, I also noticed this info message in the error view:
> org.eclipse.rse.core
> Saved passwords are not available for migration to secure storage. Deprecated authorization classes (org.eclipse.core.runtime.compatibility.auth) are not installed.
> I wonder if this is related? Do we require authentication to get the list of deployment scanners?
> BTW, org.eclipse.core.runtime.compatibility was removed in JBIDE-21382 and I suggested org.eclipse.core.runtime.compatibility.auth may be removed too -  JBIDE-22602. But as of now it's still in the TP.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)