This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Managing list of remote hosts and their property should be done as a service that 1) can be used by different NB modules 2) using this service by a module shouldn't force this module to depend on other cnd modules 3) a module should be able to contribute its own properties, UI elements and setup steps Now (1) is stisfied, but (2) and (3) are not.
Integrated into 'main-golden', will be available in build *201001271614* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/226e05b24bc3 User: Vladimir Kvashin <vkvashin@netbeans.org> Log: #179464 Remote as a service - preliminary api
Native execution is a part of IDE cluster now. So connection to the host can be established without dependencies on CND. But there is no IDE-level hosts registry/hosts properties/connection properties, etc... So, for example, there is no way to clear stored password or to change the authentication type.. etc.. This should be considered as a part of this RAS (remote as a service).
(In reply to comment #2) > Native execution is a part of IDE cluster now. So connection to the host can be > established without dependencies on CND. But there is no IDE-level hosts > registry/hosts properties/connection properties, etc... > > So, for example, there is no way to clear stored password or to change the > authentication type.. etc.. From this reason, I don't think that this issue (or at least this particular part) is an enhancement anymore. Thanks.