April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22190) Application wizard: Support "URL" templates to create a new application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22190?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22190: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application wizard: Support "URL" templates to create a new application > ----------------------------------------------------------------------- > > Key: JBIDE-22190 > URL: https://issues.jboss.org/browse/JBIDE-22190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Currently, we can choose on the server template or to use a local template. it would be nice to be able to use an URL template too. > My current use case: I want to create a Fuse Integration Service application based on a template which is available on github at https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22190) Application wizard: Support "URL" templates to create a new application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22190?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22190: ------------------------------------- Affects Version/s: 4.4.0.Alpha1 > Application wizard: Support "URL" templates to create a new application > ----------------------------------------------------------------------- > > Key: JBIDE-22190 > URL: https://issues.jboss.org/browse/JBIDE-22190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Currently, we can choose on the server template or to use a local template. it would be nice to be able to use an URL template too. > My current use case: I want to create a Fuse Integration Service application based on a template which is available on github at https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22067) Server Adapter: Need a way to restart modules

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22067?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22067. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Server Adapter: Need a way to restart modules > --------------------------------------------- > > Key: JBIDE-22067 > URL: https://issues.jboss.org/browse/JBIDE-22067 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > When doing hot code reload in an OpenShift deployed EAP server, changing a method signature will make the debugger complain with > !http://content.screencast.com/users/fbricon/folders/Jing/media/623c96cc-ae62-441b-b498-a39d9cf9b563/00000322.png|width=650! > Triggering a full publish on the module is not sufficient. > We need to at least have a way to trigger a module restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Make deletion of OpenShift resources more robust

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22241: --------------------------------------- using queries {code}project = jbide and component in (openshift) and text ~ "deletion" and status = open{code} {code}project = jbide and component in (openshift) and text ~ "delete" and status = open{code} {code}project = jbide and component in (openshift) and text ~ "service" and status = open{code} I've found just two issues which are related to this, well to deletion process of resources. I will link them to this issue as related. Unfortunately I was not able to find the one you are mentioning. > OpenShift Explorer: Make deletion of OpenShift resources more robust > -------------------------------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3, ux > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22070) "Open in Web browser" displays a dialog to select a route

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22070?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22070. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > "Open in Web browser" displays a dialog to select a route > --------------------------------------------------------- > > Key: JBIDE-22070 > URL: https://issues.jboss.org/browse/JBIDE-22070 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > I have an OpenShift project with 2 services: one {{eap-app}} and one NodeJS. > For the {{eap-app}} service, I have a corresponding server adapter. > When I select {{<eap-app server adapter> > Show In > Web Browser}}, I have the following dialog to select a route, but that seems wrong because I already selected the {{eap-app}} service, so there's no reason to propose me the route to the NodeJS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22239: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.0.Alpha2) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22239: ------------------------------------- Labels: openshift_v3 (was: ) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22237) Properties: table is not updated when resource is selected and edited

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22237 at 4/25/16 9:02 AM: ------------------------------------------------------------------- I would merge this only once we fixed JBIDE-22243 or update this issue to be reproducible with different steps. was (Author: adietish): I would merge this only once we fixed JBIDE-22243. > Properties: table is not updated when resource is selected and edited > --------------------------------------------------------------------- > > Key: JBIDE-22237 > URL: https://issues.jboss.org/browse/JBIDE-22237 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > Attachments: error-upon-scale-down.png > > > When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync. > steps to reproduce: > # ASSERT: make sure that you have at least 1 application in OpenShift > # EXEC: in Explorer: select your service > # EXEC: open up Properties and select "Deployments" tab > # EXEC: pick "Scale > Up" in the context menu > # EXEC: pick "Scale > Down" in the context menu > Result: > An error is popping up telling you that the resource is outdated. > !error-upon-scale-down.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22077) Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22077?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22077. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Pod Log and Port Fowarding are not sending the insecure-skip-tls-verify flag > ---------------------------------------------------------------------------- > > Key: JBIDE-22077 > URL: https://issues.jboss.org/browse/JBIDE-22077 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > On a machine where ~/.kube is missing or no insecure-skip-tls-verify was set from CLI, pod logs and port forwarding are failing with "Unable to connect to the server: x509: certificate signed by unknown authority" > There are 2 problems: > - the restclient is not passing the options through the oc binary > - the portforwarding code in eclipse is not sending the options to the client -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22237) Properties: table is not updated when resource is selected and edited

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22237: ------------------------------------------ I would merge this only once we fixed JBIDE-22243. > Properties: table is not updated when resource is selected and edited > --------------------------------------------------------------------- > > Key: JBIDE-22237 > URL: https://issues.jboss.org/browse/JBIDE-22237 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > Attachments: error-upon-scale-down.png > > > When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync. > steps to reproduce: > # ASSERT: make sure that you have at least 1 application in OpenShift > # EXEC: in Explorer: select your service > # EXEC: open up Properties and select "Deployments" tab > # EXEC: pick "Scale > Up" in the context menu > # EXEC: pick "Scale > Down" in the context menu > Result: > An error is popping up telling you that the resource is outdated. > !error-upon-scale-down.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 April 2016