March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21611) Reduce bloat in CDK server adapter menus

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21611?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21611: ------------------------------------- I can't remove anything in the primary menu. In the show-in menu, I can only remove Web Browser and Server Log, and that would take some effort. Server log is a bit of an outdated concept that doesn't seem to be used widely outside of astools, and even we use it only sporadically, certainly not enough. The web browser action, on the other hand, is tougher because clients *do* use it... and for some clients, it makes more sense to keep the action (but disabled) when no URL is available. So we'd need additional API for showsWebBrowserAction() vs getWelcomePageUrl(). I'll have to investigate the welcome page situation.... the server log currently has no API limiting it's addition to the menu at all. > Reduce bloat in CDK server adapter menus > ---------------------------------------- > > Key: JBIDE-21611 > URL: https://issues.jboss.org/browse/JBIDE-21611 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: cdk-server-menus.png > > > The CDK server adapter menus display a lot of useless/disabled menus: > !cdk-server-menus.png|width=650! > It'd be nice to clean that up. Keep > -(re)start > -stop > -Show in> OpenShift, Docker > -Delete > -rename > -properties > It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean some of the menus we "own". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21611) Reduce bloat in CDK server adapter menus

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21611?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21611: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Reduce bloat in CDK server adapter menus > ---------------------------------------- > > Key: JBIDE-21611 > URL: https://issues.jboss.org/browse/JBIDE-21611 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: cdk-server-menus.png > > > The CDK server adapter menus display a lot of useless/disabled menus: > !cdk-server-menus.png|width=650! > It'd be nice to clean that up. Keep > -(re)start > -stop > -Show in> OpenShift, Docker > -Delete > -rename > -properties > It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean some of the menus we "own". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21611) Reduce bloat in CDK server adapter menus

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21611?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21611: ----------------------------------- Assignee: Rob Stryker > Reduce bloat in CDK server adapter menus > ---------------------------------------- > > Key: JBIDE-21611 > URL: https://issues.jboss.org/browse/JBIDE-21611 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: cdk-server-menus.png > > > The CDK server adapter menus display a lot of useless/disabled menus: > !cdk-server-menus.png|width=650! > It'd be nice to clean that up. Keep > -(re)start > -stop > -Show in> OpenShift, Docker > -Delete > -rename > -properties > It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean some of the menus we "own". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21606: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21606: ----------------------------------- Assignee: Rob Stryker > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21606: ------------------------------------- > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. I wouldn't say 'no way', I'd just say it wasn't a priority. As more usecases come up, it helps the case for taking action. > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21814) Remove --provision flag from CDK Server launch config

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21814?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21814: ----------------------------------- Assignee: Fred Bricon (was: Rob Stryker) > Remove --provision flag from CDK Server launch config > ----------------------------------------------------- > > Key: JBIDE-21814 > URL: https://issues.jboss.org/browse/JBIDE-21814 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > When using the latest CDK, calling vagrant up with the --provision flag is unnecessary, as the openshift service now starts automatically, and harmful, as it causes the IP address of the image to change, which makes the vagrant process exit with an error. > --provision should be removed from the default launch configuration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21814) Remove --provision flag from CDK Server launch config

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21814?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21814: ----------------------------------- Fix Version/s: 4.3.1.CR1 > Remove --provision flag from CDK Server launch config > ----------------------------------------------------- > > Key: JBIDE-21814 > URL: https://issues.jboss.org/browse/JBIDE-21814 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > When using the latest CDK, calling vagrant up with the --provision flag is unnecessary, as the openshift service now starts automatically, and harmful, as it causes the IP address of the image to change, which makes the vagrant process exit with an error. > --provision should be removed from the default launch configuration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21814) Remove --provision flag from CDK Server launch config

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21814?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21814: -------------------------------------- Assignee: Rob Stryker > Remove --provision flag from CDK Server launch config > ----------------------------------------------------- > > Key: JBIDE-21814 > URL: https://issues.jboss.org/browse/JBIDE-21814 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > > When using the latest CDK, calling vagrant up with the --provision flag is unnecessary, as the openshift service now starts automatically, and harmful, as it causes the IP address of the image to change, which makes the vagrant process exit with an error. > --provision should be removed from the default launch configuration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21814) Remove --provision flag from CDK Server launch config

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21814: ----------------------------------- Summary: Remove --provision flag from CDK Server launch config Key: JBIDE-21814 URL: https://issues.jboss.org/browse/JBIDE-21814 Project: Tools (JBoss Tools) Issue Type: Task Components: cdk Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon When using the latest CDK, calling vagrant up with the --provision flag is unnecessary, as the openshift service now starts automatically, and harmful, as it causes the IP address of the image to change, which makes the vagrant process exit with an error. --provision should be removed from the default launch configuration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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