[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17180.
---------------------------------
Resolution: Done
Pushed to master+maintenance: https://github.com/jbosstools/jbosstools-server/pull/308
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: JBIDE-17180v2.png, wide-window.png
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> 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.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17180:
--------------------------------
Attachment: JBIDE-17180v2.png
Screenshot with max width on label plus wrap.
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: JBIDE-17180v2.png, wide-window.png
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> 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.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months
[JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-13445.
---------------------------------
Fix Version/s: 4.2.1.CR1
(was: 4.2.x)
Resolution: Done
Works in 4.2.1 as expected
> 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)
10 years, 11 months
[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17818:
------------------------------------------------
https://github.com/jbosstools/jbosstools-vpe/pull/294 - pull request for respin. Waiting for +1.
> Visual Editor: Need to handle external html / htm files
> -------------------------------------------------------
>
> Key: JBIDE-17818
> URL: https://issues.jboss.org/browse/JBIDE-17818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Konstantin Marmalyukov
> Labels: new_and_noteworthy, respin-a
> Fix For: 4.2.1.CR1
>
>
> Now VPE / HTML Preview can handle only workspace's files. Need to add external files support
> When I open html pages outside eclipse workspace I get an error stating VPE preview cannot open the file.
> That is not ok.
> preview should be able to just fine preview the html no matter where the content is from and if it is because some current limitation about preview then users should at least be able to edit files even if external to the workspace.
> by external to workspace I mean what is opened with File > Open File...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 11 months