[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-17818 at 12/1/14 1:37 PM:
-----------------------------------------------------------------
Here are my concerns:
1. There is no test for https://github.com/jbosstools/jbosstools-vpe/pull/294
- It's OK for 4.2.x if [~vpakan] can test it. But I would add some tests for master (a separate issue?)
2. There is a new API (new public static method for EditorUtil.java)
- Let's move this new method to VpvView.java as private for 4.2.x.
was (Author: akazakov):
Here are my concerns:
1. There is no test for https://github.com/jbosstools/jbosstools-vpe/pull/294
- It's OK for 4.2.x if [~vpakan] can test it. But I would add some tests for master (a separate issue?)
2. There is a new API (new public static method for EditorUtil.java)
- Let's move this new method to VpvView.java as private for 4.2.x.
> 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
[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-17818:
----------------------------------------
Here are my concerns:
1. There is no test for https://github.com/jbosstools/jbosstools-vpe/pull/294
- It's OK for 4.2.x if [~vpakan] can test it. But I would add some tests for master (a separate issue?)
2. There is a new API (new public static method for EditorUtil.java)
- Let's move this new method to VpvView.java as private for 4.2.x.
> 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
[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-17180:
----------------------------------------
Please, guys, all fixes committed to 4.2.x this week, should be targeted as 4.2.1.CR1 + "respin-a" label.
> 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
> Labels: respin-a
> Fix For: 4.2.1.CR1, 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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17180:
-----------------------------------
Fix Version/s: 4.2.1.CR1
(was: 4.2.1.Final)
> 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
> Labels: respin-a
> Fix For: 4.2.1.CR1, 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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17180:
-----------------------------------
Labels: respin-a (was: )
> 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
> Labels: respin-a
> Fix For: 4.2.1.CR1, 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