October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23374) Update dites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.central/4.4.1.Final/compositeArtifacts.xml return 404 errors

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23374?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-23374: ------------------------------------ Assignee: Nick Boldt > Update dites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... return 404 errors > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23374 > URL: https://issues.jboss.org/browse/JBIDE-23374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.2.AM2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > > http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... includes references to: > * http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.1.Final > * http://download.jboss.org/jbosstools/neon/staging/updates/central/4.4.1.F... > Both of these links return 404 errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23374) Update dites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.central/4.4.1.Final/compositeArtifacts.xml return 404 errors

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-23374: ------------------------------------ Summary: Update dites referenced in http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... return 404 errors Key: JBIDE-23374 URL: https://issues.jboss.org/browse/JBIDE-23374 Project: Tools (JBoss Tools) Issue Type: Bug Components: central-update Affects Versions: 4.4.2.AM2 Reporter: Len DiMaggio http://download.jboss.org/jbosstools/neon/staging/updates/discovery.centr... includes references to: * http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.1.Final * http://download.jboss.org/jbosstools/neon/staging/updates/central/4.4.1.F... Both of these links return 404 errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23147) application wizard: Support optional host when route is created

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23147?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23147. --------------------------------- Verified in DevStudio 10.2.0.AM2 build AM2-v20161014-0456-B6202. > application wizard: Support optional host when route is created > --------------------------------------------------------------- > > Key: JBIDE-23147 > URL: https://issues.jboss.org/browse/JBIDE-23147 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: application_wizard, new_and_noteworthy, openshift_v3 > Fix For: 4.4.2.AM2 > > > When an application is created and route option is selected, the host is generated by default but user should have the option to set it (as in web console) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23373) Application Wizard: Connection info could be visible on first wizard page

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23373?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23373: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application Wizard: Connection info could be visible on first wizard page > ------------------------------------------------------------------------- > > Key: JBIDE-23373 > URL: https://issues.jboss.org/browse/JBIDE-23373 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > In New OpenShift Application wizard on the first wizard page there is a project combo to choose a project for a new application. We are missing a connection info on this page so user don't see for which connection is an application created. It seems to be obvious, that it is for selected project from OpenShift Explorer (if view is visible = modal dialog is not on top of it at that moment) but in case of several connections with same project, it could cause troubles. > We could have it similar as it is in Deploy Docker Image wizard, where we display connection info. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23373) Application Wizard: Connection info could be visible on first wizard page

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-23373: ------------------------------------- Summary: Application Wizard: Connection info could be visible on first wizard page Key: JBIDE-23373 URL: https://issues.jboss.org/browse/JBIDE-23373 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.2.AM2 Reporter: Marián Labuda In New OpenShift Application wizard on the first wizard page there is a project combo to choose a project for a new application. We are missing a connection info on this page so user don't see for which connection is an application created. It seems to be obvious, that it is for selected project from OpenShift Explorer (if view is visible = modal dialog is not on top of it at that moment) but in case of several connections with same project, it could cause troubles. We could have it similar as it is in Deploy Docker Image wizard, where we display connection info. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4110) New project always created under default namespace Openshift v3 Eclipse Tooling

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4110?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-4110. ------------------------------- Closing as a duplicate. Has been resolved in DevStudio 10.2.0.AM2. > New project always created under default namespace Openshift v3 Eclipse Tooling > ------------------------------------------------------------------------------- > > Key: JBDS-4110 > URL: https://issues.jboss.org/browse/JBDS-4110 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: !Screen Shot 2016-10-12 at 4.17.54 PM.png|thumbnail! > !Screen Shot 2016-10-12 at 4.17.45 PM.png|thumbnail! > !Screen Shot 2016-10-12 at 4.17.18 PM.png|thumbnail! > Reporter: Zak Hassan > Assignee: Jeff MAURY > Fix For: 10.2.0.AM2 > > Attachments: Screen Shot 2016-10-12 at 4.16.11 PM.png, Screen Shot 2016-10-12 at 4.17.18 PM.png, Screen Shot 2016-10-12 at 4.17.45 PM.png, Screen Shot 2016-10-12 at 4.17.54 PM.png > > > When creating a new project using eclipse openshift plugin dev studio. I specifically request to create an application under namespace "fsoss2016" but get my application created under default namespace Openshift v3 Eclipse Tooling. > See image below: > !Screen Shot 2016-10-12 at 4.16.11 PM.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4110) New project always created under default namespace Openshift v3 Eclipse Tooling

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4110?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-4110: -------------------------------- Sprint: (was: devex #122 October 2016) > New project always created under default namespace Openshift v3 Eclipse Tooling > ------------------------------------------------------------------------------- > > Key: JBDS-4110 > URL: https://issues.jboss.org/browse/JBDS-4110 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: !Screen Shot 2016-10-12 at 4.17.54 PM.png|thumbnail! > !Screen Shot 2016-10-12 at 4.17.45 PM.png|thumbnail! > !Screen Shot 2016-10-12 at 4.17.18 PM.png|thumbnail! > Reporter: Zak Hassan > Assignee: Jeff MAURY > Fix For: 10.2.0.AM2 > > Attachments: Screen Shot 2016-10-12 at 4.16.11 PM.png, Screen Shot 2016-10-12 at 4.17.18 PM.png, Screen Shot 2016-10-12 at 4.17.45 PM.png, Screen Shot 2016-10-12 at 4.17.54 PM.png > > > When creating a new project using eclipse openshift plugin dev studio. I specifically request to create an application under namespace "fsoss2016" but get my application created under default namespace Openshift v3 Eclipse Tooling. > See image below: > !Screen Shot 2016-10-12 at 4.16.11 PM.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22914) OpenShift Deployment: Deploy latest does not work correctly

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22914?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22914: ---------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.2.AM2) > OpenShift Deployment: Deploy latest does not work correctly > ----------------------------------------------------------- > > Key: JBIDE-22914 > URL: https://issues.jboss.org/browse/JBIDE-22914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: openshift_v3 > Fix For: 4.4.2.Final > > > When I have an application where no replication controller is yet and I want to deploy latest, I get following error: > {code} > Unable to perform a deployment for config hello-openshift > com.openshift.restclient.NotFoundException: replicationcontrollers "hello-openshift-0" not found > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:105) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:59) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:200) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:181) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:269) > at com.openshift.internal.restclient.capability.resources.DeployCapability.deploy(DeployCapability.java:59) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:90) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1.doRun(TriggerDeploymentHandler.java:85) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is wrong, because it is trying to "deploy latest replication controller" instead of deploying latest deployment configuration (as it works e.g. from oc binary - deployment uses latest deployment configuration not replication controller which could be understood as instance of deployment configuration). Therefore if there is no replication controller and I click Deploy Latest in context menu of a service in OpenShift Explorer view or in context menu of a deployment configuration in properties view, I get the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22914) OpenShift Deployment: Deploy latest does not work correctly

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22914?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov resolved JBIDE-22914. -------------------------------------- Resolution: Done it was fixed in restclient only and currently AM2 uses version (openshift-restclient-java-5.2.0-20161013.193442-9) that doesn't contain the fix yet. Everything should be fine when the version is switched to openshift-restclient-java-5.2.0-20161014.173515-10 > OpenShift Deployment: Deploy latest does not work correctly > ----------------------------------------------------------- > > Key: JBIDE-22914 > URL: https://issues.jboss.org/browse/JBIDE-22914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: openshift_v3 > Fix For: 4.4.2.AM2 > > > When I have an application where no replication controller is yet and I want to deploy latest, I get following error: > {code} > Unable to perform a deployment for config hello-openshift > com.openshift.restclient.NotFoundException: replicationcontrollers "hello-openshift-0" not found > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:105) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:59) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:200) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:181) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:269) > at com.openshift.internal.restclient.capability.resources.DeployCapability.deploy(DeployCapability.java:59) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:90) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1.doRun(TriggerDeploymentHandler.java:85) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is wrong, because it is trying to "deploy latest replication controller" instead of deploying latest deployment configuration (as it works e.g. from oc binary - deployment uses latest deployment configuration not replication controller which could be understood as instance of deployment configuration). Therefore if there is no replication controller and I click Deploy Latest in context menu of a service in OpenShift Explorer view or in context menu of a deployment configuration in properties view, I get the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23372) Resource wizard: lots of empty space to the right of the project settings

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23372?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23372: ------------------------------------- Attachment: empty-horiz-space.png > Resource wizard: lots of empty space to the right of the project settings > ------------------------------------------------------------------------- > > Key: JBIDE-23372 > URL: https://issues.jboss.org/browse/JBIDE-23372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Attachments: empty-horiz-space.png > > > In wizard to create new resources the 1st line that allows one to select the OpenShift project, there's plenty of space to the right. The project combo should be sclaed to use all the available horizontal space so that the widgets are nicely aligned > !empty-horiz-space.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016