January 2016 - jbosstools-issues - Jboss List Archives

[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 commented on JBIDE-21603: ------------------------------------- [~ldimaggio] Nope... it was there just in case we decided to do deployment to the cdk directly. It's really 100% a stub that can be safely ignored or we can remove it. I'd put it at a low priority (since it can be safely ignored) but it's still something that could be cleaned up. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3585) Update support matrix to include OS X El Capitan (10.11)

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3585?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-3585: -------------------------------------- [~mhusnain] please add corresponding TOOLSDOC Jira for this so it's affected on configuration pages. Thanks :) > Update support matrix to include OS X El Capitan (10.11) > -------------------------------------------------------- > > Key: JBDS-3585 > URL: https://issues.jboss.org/browse/JBDS-3585 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Fix For: 9.1.0.Beta2 > > > OS X El Capitan 10.11 was released in autumn 2015 and we actually tested JBDS 9.0 with it already, but it was too late to change the support matrix. So let's do it for JBDS 9.1. > I suggest to have the latest two versions for JBDS 9.1, i.e. Yosemite and El Capitan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3585) Update support matrix to include OS X El Capitan (10.11)

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3585?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3585: ----------------------------------- This issue is not setup for CDW, so +1 in the comments :-) > Update support matrix to include OS X El Capitan (10.11) > -------------------------------------------------------- > > Key: JBDS-3585 > URL: https://issues.jboss.org/browse/JBDS-3585 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Fix For: 9.1.0.Beta2 > > > OS X El Capitan 10.11 was released in autumn 2015 and we actually tested JBDS 9.0 with it already, but it was too late to change the support matrix. So let's do it for JBDS 9.1. > I suggest to have the latest two versions for JBDS 9.1, i.e. Yosemite and El Capitan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3575: ----------------------------- > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.CR1 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-3575: ------------------------------ Status: New (was: New) > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.CR1 > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21603) CDK Runtime is useless stub and should be removed

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-21603: -------------------------------------- Do we/the users lose ANYTHING useful if it is removed? > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-21608: ---------------------------------- Description: This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. So for Livereload, there are these two items that should be disabled on an ejb module: Show in -> Web Browser via Livereload Show in -> Web Browser on External device was: This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. > "Show In -> Web Browser via Live Reload" on EJB module should be disabled > ------------------------------------------------------------------------- > > Key: JBIDE-21608 > URL: https://issues.jboss.org/browse/JBIDE-21608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > > This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. > Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. > So for Livereload, there are these two items that should be disabled on an ejb module: > Show in -> Web Browser via Livereload > Show in -> Web Browser on External device -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21138) "Show In -> Web Browser" on EJB module does nothing.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21138?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21138. --------------------------------- This was verified by Radim. But it's just "Show in -> Web browser" that was disabled. There are others that need to be disabled also - livereload and browsersim: JBIDE-21608 JBIDE-21607 > "Show In -> Web Browser" on EJB module does nothing. > ---------------------------------------------------- > > Key: JBIDE-21138 > URL: https://issues.jboss.org/browse/JBIDE-21138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151122-1948-B143 > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > As title says... Selecting "Show In -> Web Browser" on EJB module does nothing. I would expect this option to be disabled, or web browser to be opened with 404 page. Instead of this, nothing happens. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21608: --------------------------------------- [~rob.stryker] can help if needed. > "Show In -> Web Browser via Live Reload" on EJB module should be disabled > ------------------------------------------------------------------------- > > Key: JBIDE-21608 > URL: https://issues.jboss.org/browse/JBIDE-21608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > > This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. > Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21607) "Show In -> Browsersim" on EJB module should be disabled

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21607?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21607: --------------------------------------- [~rob.stryker] can help if needed. > "Show In -> Browsersim" on EJB module should be disabled > -------------------------------------------------------- > > Key: JBIDE-21607 > URL: https://issues.jboss.org/browse/JBIDE-21607 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > > This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. > Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

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 January 2016