[JBoss JIRA] (JBIDE-24188) CDKv3 terminal output in IDE is ugly when using hyperv
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24188?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24188:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> CDKv3 terminal output in IDE is ugly when using hyperv
> ------------------------------------------------------
>
> Key: JBIDE-24188
> URL: https://issues.jboss.org/browse/JBIDE-24188
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Environment: Windows 10, x86_64, hyper V.
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: Terminal-HyperV.png, cdk3-hyperv-terminal
>
>
> While starting/stopping CDKv3 server adapter, you can observe flashing window (coming from hyperV) in terminal tab. The output looks bit ugly, there is pretty much space. When starting/stoping minishift from windows command prompt, you can see such blue flashing/blinking window, too. When I tried cygwin terminal, this did not happen. I am not sure if we can do anything about it, it seems like upstream/system issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24436) Deploy wizard: dialog expands to full available vertical space
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24436?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24436:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Deploy wizard: dialog expands to full available vertical space
> --------------------------------------------------------------
>
> Key: JBIDE-24436
> URL: https://issues.jboss.org/browse/JBIDE-24436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.x
>
> Attachments: deploy-image-wizard-too-tall.png
>
>
> steps:
> # ASSERT: have a docker image available in your local docker daemon
> # ASSERT: have docker tooling installed and a connection to your local docker daemon defined
> # EXEC: open "Docker Explorer" view, unfold "Images" for the conneciton to your local docker daemon
> # EXEC: select your docker image and pick "Deploy to OpenShift..."
> Result:
> Docker Image deploy wizard pops up, taking all the available vertical space
> !deploy-image-wizard-too-tall.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22862) Example "." found when searching for a Camel quickstart
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22862?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22862:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Example "." found when searching for a Camel quickstart
> -------------------------------------------------------
>
> Key: JBIDE-22862
> URL: https://issues.jboss.org/browse/JBIDE-22862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.4.1.AM1
> Environment: JBoss Fuse Tools must be installed
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.5.x
>
>
> When the JBoss Fuse tools are installes, the Camel examples are available in JBoss Central. If you search for Camel, An example named "." is returned. It fails to import.
> See !http://content.screencast.com/users/fbricon/folders/Jing/media/36fb717a-1cd8-4c6a-8c25-b74d46c4c6be/00000447.png|width=700!
> That example should not be returned.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21895:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Application wizard: Resource name collisions after deleting and recreating the application
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Labels: application_wizard, openshift_v3
> Fix For: 4.5.x
>
> Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
> Result:
> !Screen Shot 2016-03-17 at 16.19.05.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22750) Auto-insert name after </# and </@
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22750?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22750:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Auto-insert name after </# and </@
> ----------------------------------
>
> Key: JBIDE-22750
> URL: https://issues.jboss.org/browse/JBIDE-22750
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Daniel Dekany
> Fix For: 4.5.x
>
>
> It would be very handy if {{<#/}} auto-inserts the name of directive that it closes. It's tricky to do though, because it has to be synchronous (and fast) and so it certainly can't wait for the result from the reconciler thread. Without that, finding out what tag needs closing isn't trivial because most but not all {{#}} directives are implicitly closed (worse, in case of assignments that depends on the expression after the directive name).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months