March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22047) Label Openshift CDK feature as "Tech Preview"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22047?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22047: ------------------------------- Description: Per call today, openshift.cdk.feature should be clearly marked as Tech Preview (was: Per call today, openshift.cdk.feature should be clearly marked as Tech Preview, and its version should be downgraded from CR1 to Alpha.) > Label Openshift CDK feature as "Tech Preview" > --------------------------------------------- > > Key: JBIDE-22047 > URL: https://issues.jboss.org/browse/JBIDE-22047 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk, openshift > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.CR1 > > > Per call today, openshift.cdk.feature should be clearly marked as Tech Preview -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21995) Hostname is set to localhost when prompt for route is checked

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21995: ----------------------------------------------- [~xcoulon], your patch in livereload supports the design for openshift 3 server adapter that in a somewhat unusual way makes host a variable that can be set/modified after Show in action is called. Maybe this design will bump into other problems unseen yet, but at least with livereload you have solved it (I added some comments to the pull request on behaviour of getWelcomePageUrl() method). > Hostname is set to localhost when prompt for route is checked > ------------------------------------------------------------- > > Key: JBIDE-21995 > URL: https://issues.jboss.org/browse/JBIDE-21995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22041) Exception is thrown when I do not want to open cheatsheet

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22041?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22041: ----------------------------------- Assignee: Snjezana Peco > Exception is thrown when I do not want to open cheatsheet > --------------------------------------------------------- > > Key: JBIDE-22041 > URL: https://issues.jboss.org/browse/JBIDE-22041 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.OperationCanceledException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.promptToShowCheatsheets(CheatSheetUtil.java:434) > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.access$1(CheatSheetUtil.java:394) > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil$1.run(CheatSheetUtil.java:378) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22050) Cannot show OpenShift 3 application via live reload on a module

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22050?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22050: ---------------------------------- > Cannot show OpenShift 3 application via live reload on a module > --------------------------------------------------------------- > > Key: JBIDE-22050 > URL: https://issues.jboss.org/browse/JBIDE-22050 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, openshift > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Labels: openshift_v3, server_adapter > > Currently Show In - Web Browser via Live Reload Server does not work for OpenShift 3 server adapter. It opens url localhost:port but a page is empty. Page is of type text/plain. > There is also a question - do we really need showing via live reload anymore? We have already incremental deployment what reflect similar(/same) behaviour as Live Reload. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22050) Cannot show OpenShift 3 application via live reload on a module

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-22050: ------------------------------------- Summary: Cannot show OpenShift 3 application via live reload on a module Key: JBIDE-22050 URL: https://issues.jboss.org/browse/JBIDE-22050 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload, openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Xavier Coulon Priority: Critical Fix For: 4.3.1.CR1 Currently Show In - Web Browser via Live Reload Server does not work for OpenShift 3 server adapters. It opens url localhost:port but a page is empty. Page is of type text/plain. There is also a question - do we really need showing via live reload anymore? We have already incremental deployment what reflect similar(/same) behaviour as Live Reload. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22010) For JBIDE 4.3.1.CR1: Prepare for Final/GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22010?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22010: ------------------------------------ Jobs have been updated to use the releng-publish tools from 4.3.1.Final-SNAPSHOT and the latest .Final TPs too. https://github.com/jbdevstudio/jbdevstudio-ci/commit/d3e5fd468a60545be011... > For JBIDE 4.3.1.CR1: Prepare for Final/GA > ----------------------------------------- > > Key: JBIDE-22010 > URL: https://issues.jboss.org/browse/JBIDE-22010 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3740 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21995) Hostname is set to localhost when prompt for route is checked

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21995: --------------------------------------- [~fbricon] ok, thanks for your feedback, I'll apply your comments on the LR patch and merge it, then. > Hostname is set to localhost when prompt for route is checked > ------------------------------------------------------------- > > Key: JBIDE-21995 > URL: https://issues.jboss.org/browse/JBIDE-21995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22047) Label Openshift CDK feature as "Tech Preview" and ensure version is Alpha, not Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22047?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22047: ------------------------------------ [~akazakov] Once we confirm what needs to be done here, I can concoct a PR to force the single openshift.cdk feature to be Alpha while the rest of the plugins in that project are CR/Final, and add the "Tech Preview" description into the feature.properties file. > Label Openshift CDK feature as "Tech Preview" and ensure version is Alpha, not Final > ------------------------------------------------------------------------------------ > > Key: JBIDE-22047 > URL: https://issues.jboss.org/browse/JBIDE-22047 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk, openshift > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.CR1 > > > Per call today, openshift.cdk.feature should be clearly marked as Tech Preview, and its version should be downgraded from CR1 to Alpha. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22047) Label Openshift CDK feature as "Tech Preview" and ensure version is Alpha, not Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22047?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22047: ---------------------------------- Assignee: Alexey Kazakov > Label Openshift CDK feature as "Tech Preview" and ensure version is Alpha, not Final > ------------------------------------------------------------------------------------ > > Key: JBIDE-22047 > URL: https://issues.jboss.org/browse/JBIDE-22047 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk, openshift > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.CR1 > > > Per call today, openshift.cdk.feature should be clearly marked as Tech Preview, and its version should be downgraded from CR1 to Alpha. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21992: ----------------------------------------------- I have opened issues JBIDE-22031 and JBIDE-22032. For the first one (Set message to "Deployment Configuration & Scalability" page of Deploy Docker Image wizard) the main issue is to compose a nice message. Could you suggest it please? > Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21992 > URL: https://issues.jboss.org/browse/JBIDE-21992 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard > Fix For: 4.3.1.CR1 > > Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png > > > The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way. > !deploy-config-scalability-page.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 March 2016