[JBoss JIRA] (JBDS-3710) use brackets logo for big installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3710 at 3/23/16 7:28 PM:
--------------------------------------------------------------
Current logo is jpg file
!https://raw.githubusercontent.com/redhat-developer-tooling/developer-platform-install/master/browser/images/Logo.jpg!
which is shown as 180x59px.
was (Author: dgolovin):
Current logo is jpg file
!https://raw.githubusercontent.com/redhat-developer-tooling/developer-platform-install/master/browser/images/Logo.jpg!
which is shown with width 180px.
> use brackets logo for big installer
> -----------------------------------
>
> Key: JBDS-3710
> URL: https://issues.jboss.org/browse/JBDS-3710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Reporter: Max Rydahl Andersen
> Priority: Blocker
>
> based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big installer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3710) use brackets logo for big installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3710:
-------------------------------------
Current logo is jpg file
!https://raw.githubusercontent.com/redhat-developer-tooling/developer-platform-install/master/browser/images/Logo.jpg!
which is shown with width 180px.
> use brackets logo for big installer
> -----------------------------------
>
> Key: JBDS-3710
> URL: https://issues.jboss.org/browse/JBDS-3710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Reporter: Max Rydahl Andersen
> Priority: Blocker
>
> based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big installer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21603) CDK Runtime is useless stub and should be removed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21603.
---------------------------------
Resolution: Done
removed
{code}
commit 3279fd324c37ea45e0cac8c4570e5bf0a390f3e9
Author: Rob Stryker <rob(a)oxbeef.net>
Date: Wed Mar 23 19:17:04 2016 -0400
JBIDE-21603 - removing useless ui element for cdk runtime
one-line fix that just sets runtime=false
diff --git a/plugins/org.jboss.tools.openshift.cdk.server/plugin.xml b/plugins/org.jboss.tools.openshift.cdk.server/plugin.xml
index a693ce2..25d5aae 100644
--- a/plugins/org.jboss.tools.openshift.cdk.server/plugin.xml
+++ b/plugins/org.jboss.tools.openshift.cdk.server/plugin.xml
@@ -13,7 +13,7 @@
initialState="stopped"
launchConfigId="org.jboss.tools.openshift.cdk.server.core.internal.behaviour.launchType"
launchModes="run"
- runtime="true"
+ runtime="false"
runtimeTypeId="org.jboss.tools.openshift.cdk.server.runtime.type"
startBeforePublish="false"
startTimeout="1800000"
{code}
> CDK Runtime is useless stub and should be removed
> -------------------------------------------------
>
> Key: JBIDE-21603
> URL: https://issues.jboss.org/browse/JBIDE-21603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21953) xip.io not working on Windows
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21953:
-------------------------------------
[~mmalina] Since you're in the office pretty often, it might be best if you try to set up a triage session with them if possible. I'm sure you can provide concrete proof this affects you ;)
> xip.io not working on Windows
> -----------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Priority: Blocker
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21946) CDK server asks for password at every start
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21946?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21946.
---------------------------------
Resolution: Done
This is mostly fixed by JBIDE-21963
However, if a user refuses to save the credentials, they will still be prompted on every startup (but probably not while startups are in session, since we cache the values to the best of our ability)
> CDK server asks for password at every start
> -------------------------------------------
>
> Key: JBIDE-21946
> URL: https://issues.jboss.org/browse/JBIDE-21946
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> When I start CDK server it asks me for the password every start.
> I'm using CDK beta 5 installed by our windows installer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21949?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21949:
----------------------------------------
Not a blocker for 9.1.0 but if it's easy to fix and you can provide a PR really quickly then we can include it to the release ;)
> Allow user to turn on/off showing console when output changes
> -------------------------------------------------------------
>
> Key: JBIDE-21949
> URL: https://issues.jboss.org/browse/JBIDE-21949
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21949?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21949:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Allow user to turn on/off showing console when output changes
> -------------------------------------------------------------
>
> Key: JBIDE-21949
> URL: https://issues.jboss.org/browse/JBIDE-21949
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years