March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3574) CDK username pulldown field is not tall enough (screenshot attached)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3574?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3574: --------------------------------- Fix Version/s: 10.x > CDK username pulldown field is not tall enough (screenshot attached) > -------------------------------------------------------------------- > > Key: JBDS-3574 > URL: https://issues.jboss.org/browse/JBDS-3574 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: runtime > Affects Versions: 9.1.0.Beta1 > Environment: Version: 9.1.0.Beta1 > Build id: Beta1-v20151210-1215-B180 > Build date: 20151210-1215 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 10.x > > Attachments: Dec_10_username.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3574) CDK username pulldown field is not tall enough (screenshot attached)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3574?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3574: ------------------------------------ Assignee: Snjezana Peco [~snjeza] looks like a GTK 3 issue. Can you help with that please? > CDK username pulldown field is not tall enough (screenshot attached) > -------------------------------------------------------------------- > > Key: JBDS-3574 > URL: https://issues.jboss.org/browse/JBDS-3574 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: runtime > Affects Versions: 9.1.0.Beta1 > Environment: Version: 9.1.0.Beta1 > Build id: Beta1-v20151210-1215-B180 > Build date: 20151210-1215 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 10.x > > Attachments: Dec_10_username.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3574) CDK username pulldown field is not tall enough (screenshot attached)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3574?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3574: ----------------------------- > CDK username pulldown field is not tall enough (screenshot attached) > -------------------------------------------------------------------- > > Key: JBDS-3574 > URL: https://issues.jboss.org/browse/JBDS-3574 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: runtime > Affects Versions: 9.1.0.Beta1 > Environment: Version: 9.1.0.Beta1 > Build id: Beta1-v20151210-1215-B180 > Build date: 20151210-1215 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 10.x > > Attachments: Dec_10_username.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3574) CDK username pulldown field is not tall enough (screenshot attached)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3574?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3574: -------------------------------- > CDK username pulldown field is not tall enough (screenshot attached) > -------------------------------------------------------------------- > > Key: JBDS-3574 > URL: https://issues.jboss.org/browse/JBDS-3574 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: runtime > Affects Versions: 9.1.0.Beta1 > Environment: Version: 9.1.0.Beta1 > Build id: Beta1-v20151210-1215-B180 > Build date: 20151210-1215 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 10.x > > Attachments: Dec_10_username.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK (2.0.0.Beta5)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22004: ----------------------------------- Component/s: upstream > Runtime detection unable to detect CDK (2.0.0.Beta5) > ---------------------------------------------------- > > Key: JBIDE-22004 > URL: https://issues.jboss.org/browse/JBIDE-22004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Fix For: 4.4.x > > > Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it. > Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK (2.0.0.Beta5)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22004: -------------------------------------- Assignee: Hardy Ferentschik > Runtime detection unable to detect CDK (2.0.0.Beta5) > ---------------------------------------------------- > > Key: JBIDE-22004 > URL: https://issues.jboss.org/browse/JBIDE-22004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Hardy Ferentschik > Fix For: 4.4.x > > > Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it. > Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK (2.0.0.Beta5)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22004: ----------------------------------- Fix Version/s: 4.4.x > Runtime detection unable to detect CDK (2.0.0.Beta5) > ---------------------------------------------------- > > Key: JBIDE-22004 > URL: https://issues.jboss.org/browse/JBIDE-22004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Hardy Ferentschik > Fix For: 4.4.x > > > Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it. > Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK (2.0.0.Beta5)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22004: ----------------------------------- Issue Type: Feature Request (was: Bug) > Runtime detection unable to detect CDK (2.0.0.Beta5) > ---------------------------------------------------- > > Key: JBIDE-22004 > URL: https://issues.jboss.org/browse/JBIDE-22004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > > Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it. > Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21812) Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21812?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21812: -------------------------------------- Assignee: Rob Stryker > Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1 > ---------------------------------------------------------------------- > > Key: JBIDE-21812 > URL: https://issues.jboss.org/browse/JBIDE-21812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta2 > Environment: JBoss AS 7.1.1 > Eclipse Mars.2 4.5.2 > IPv4 stack specified > Local host connectivity (127.0.0.1 specified) > Reporter: William Darby > Assignee: Rob Stryker > Fix For: 4.4.x > > Attachments: eclipse.log > > > When starting JBoss from within Eclipse the following error appears on the console: > 17:25:23,182 ERROR [org.jboss.remoting.remote.connection] (Remoting "hostname:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine > This occurs with or without firewall/anti-virus enabled. > And with the startup/shutdown pollers set to Management Service or Web Port. > Also with Server Ports specified or 'Detected from Local Runtime' > It occurs occasionally on the first server startup, but repeatedly after stopping and restarting the server. > It also occurs when the 'Server Details' are browsed in the Servers view, i.e., selecting any folder will cause another of the errors to display. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21812) Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21812?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21812: ----------------------------------- Fix Version/s: 4.4.x > Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1 > ---------------------------------------------------------------------- > > Key: JBIDE-21812 > URL: https://issues.jboss.org/browse/JBIDE-21812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta2 > Environment: JBoss AS 7.1.1 > Eclipse Mars.2 4.5.2 > IPv4 stack specified > Local host connectivity (127.0.0.1 specified) > Reporter: William Darby > Assignee: Rob Stryker > Fix For: 4.4.x > > Attachments: eclipse.log > > > When starting JBoss from within Eclipse the following error appears on the console: > 17:25:23,182 ERROR [org.jboss.remoting.remote.connection] (Remoting "hostname:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine > This occurs with or without firewall/anti-virus enabled. > And with the startup/shutdown pollers set to Management Service or Web Port. > Also with Server Ports specified or 'Detected from Local Runtime' > It occurs occasionally on the first server startup, but repeatedly after stopping and restarting the server. > It also occurs when the 'Server Details' are browsed in the Servers view, i.e., selecting any folder will cause another of the errors to display. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016