January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22805. -------------------------------------- Resolution: Done > Add Scale... menus on Pod resources > ----------------------------------- > > Key: JBIDE-22805 > URL: https://issues.jboss.org/browse/JBIDE-22805 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.4.3.AM2 > > > I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level. > I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-22805. ------------------------------------ > Add Scale... menus on Pod resources > ----------------------------------- > > Key: JBIDE-22805 > URL: https://issues.jboss.org/browse/JBIDE-22805 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.4.3.AM2 > > > I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level. > I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23709) Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23709?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23709: ------------------------------------- Attachment: project-selected-no-scaling.png > Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23709 > URL: https://issues.jboss.org/browse/JBIDE-23709 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Attachments: project-selected-no-scaling.png, service-selected-scaling-possible.png > > > steps to reproduce: > # ASSERT: make sure that you have at least 1 service & pod running in OpenShift > # EXEC: in OpenShift Explorer: select the project that contains the service/pod > # EXEC: in Properties view: select "Pod" tab and then your running pod (not the build pod, but the pod that's running your service). Open up the context menu > Result: > "Scale" with is child entries is missing from the context menu. > !project-selected-no-scaling.png! > While it's present if you have the service selected in the OpenShift Explorer. > !service-selected-scaling-possible.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23709) Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23709?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23709: ------------------------------------- Attachment: (was: project-selected-no-scaling.png) > Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23709 > URL: https://issues.jboss.org/browse/JBIDE-23709 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Attachments: service-selected-scaling-possible.png > > > steps to reproduce: > # ASSERT: make sure that you have at least 1 service & pod running in OpenShift > # EXEC: in OpenShift Explorer: select the project that contains the service/pod > # EXEC: in Properties view: select "Pod" tab and then your running pod (not the build pod, but the pod that's running your service). Open up the context menu > Result: > "Scale" with is child entries is missing from the context menu. > !project-selected-no-scaling.png! > While it's present if you have the service selected in the OpenShift Explorer. > !service-selected-scaling-possible.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23709) Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23709?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23709: ------------------------------------- Attachment: project-selected-no-scaling.png service-selected-scaling-possible.png > Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23709 > URL: https://issues.jboss.org/browse/JBIDE-23709 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Attachments: project-selected-no-scaling.png, service-selected-scaling-possible.png > > > steps to reproduce: > # ASSERT: make sure that you have at least 1 service & pod running in OpenShift > # EXEC: in OpenShift Explorer: select the project that contains the service/pod > # EXEC: in Properties view: select "Pod" tab and then your running pod (not the build pod, but the pod that's running your service). Open up the context menu > Result: > "Scale" with is child entries is missing from the context menu. > !project-selected-no-scaling.png! > While it's present if you have the service selected in the OpenShift Explorer. > !service-selected-scaling-possible.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23709) Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23709: ---------------------------------------- Summary: Properties: Scaling To/Up/Down are missing in context menu when project is selected in explorer Key: JBIDE-23709 URL: https://issues.jboss.org/browse/JBIDE-23709 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.3.AM1 Reporter: Andre Dietisheim steps to reproduce: # ASSERT: make sure that you have at least 1 service & pod running in OpenShift # EXEC: in OpenShift Explorer: select the project that contains the service/pod # EXEC: in Properties view: select "Pod" tab and then your running pod (not the build pod, but the pod that's running your service). Open up the context menu Result: "Scale" with is child entries is missing from the context menu. !project-selected-no-scaling.png! While it's present if you have the service selected in the OpenShift Explorer. !service-selected-scaling-possible.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22816: ------------------------------------ Did test it against 10.3.0.AM1 and was not able to reproduce. I think it was fixed by JBIDE-22915 but added steps to reproduced for QE validation > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ] Aurélien Pupier updated JBTIS-1015: ----------------------------------- Steps to Reproduce: for first case: - download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B... - unzip it - windows->preferences->Plug-in development->Target Platform - Add... - check Nothing: Start with an empty target definition - Next - in Locations tab, click Add... - select "Directory" and click Next - Select the location where you unzipped the mirror - Click finish - Click Finish - ensure that you select it in the list and then click Apply and then OK - Launch an Eclipse application with all plugins - go to Servers view - configure access to CDK server - Launch the CDK server --> the JVM is crashing because the org.eclipse.cdt.core.win32.x86_64 - or the one which corresponds to your OS - is not in exploded mode for second case: - download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B... - unzip it - windows->preferences->Plug-in development->Target Platform - Add... - check Nothing: Start with an empty target definition - Next - in Locations tab, click Add... - select "Software Site" and click Next --> it complains about javax.crypto packages not available, this package is provided by the JVM was: for first case: - download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B... - unzip it - windows->preferences->Plug-in development->Target Platform - Add... - check Nothing: Start with an empty target definition - Next - in Locations tab, click Add... - select "Directory" and click Next - Select the location where you unzipped the mirror - Click finish - Click Finish - ensure that you select it in the list and then click Apply and then OK - Launch an Eclipse application with all plugins - go to Servers view - configure access to CDK server - Launch the CDK server --> the JVM is crashing because the org.eclipse.cdt.core.win32.x86_64 - or the one which corresponds to your OS - is not in exploded mode > Latest JBDSIS Target Platform cannot be used locally > ---------------------------------------------------- > > Key: JBTIS-1015 > URL: https://issues.jboss.org/browse/JBTIS-1015 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > Current state of understanding: > There are 2 different bugs: > * when using local "Directory": the jars which should be exploded in folder stay in jars > ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? > ** the implication is that we can't start a CDK server with such a TP > * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) > ** looks like a p2 bugs > ** the implication is that the TP doesn't resolve at all > If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. > see [JBTIS-1008] for original discussions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22816: ------------------------------- Steps to Reproduce: ASSERT: Have an OpenShift 3 connection with at least 2 projects eap and eap1. EXEC: Select first project and open New OpenShift Application wizard. EXEC: Select a builder image (jboss-eap64-openshift). EXEC: Finish the wizard. RESULT: Builder image resources are created on first project. EXEC: Select second project and open New OpenShift Application wizard. EXEC: Select a builder image (jboss-eap64-openshift). EXEC: Finish the wizard. RESULT: Builder image resources are created on first project. EXPECTED RESULT: Builder image resources are created on second project. > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ] Aurélien Pupier updated JBTIS-1015: ----------------------------------- Steps to Reproduce: for first case: - download the zipped mirror https://10.8.63.16/view/Fuse%20Tooling/job/Fuse-Tooling-Target-Platform-B... - unzip it - windows->preferences->Plug-in development->Target Platform - Add... - check Nothing: Start with an empty target definition - Next - in Locations tab, click Add... - select "Directory" and click Next - Select the location where you unzipped the mirror - Click finish - Click Finish - ensure that you select it in the list and then click Apply and then OK - Launch an Eclipse application with all plugins - go to Servers view - configure access to CDK server - Launch the CDK server --> the JVM is crashing because the org.eclipse.cdt.core.win32.x86_64 - or the one which corresponds to your OS - is not in exploded mode > Latest JBDSIS Target Platform cannot be used locally > ---------------------------------------------------- > > Key: JBTIS-1015 > URL: https://issues.jboss.org/browse/JBTIS-1015 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > Current state of understanding: > There are 2 different bugs: > * when using local "Directory": the jars which should be exploded in folder stay in jars > ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? > ** the implication is that we can't start a CDK server with such a TP > * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) > ** looks like a p2 bugs > ** the implication is that the TP doesn't resolve at all > If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. > see [JBTIS-1008] for original discussions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 2017