October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25309: ------------------------------- Attachment: what-the-what.png > Can't install stuff from RH Central into JBoss Tools > ---------------------------------------------------- > > Key: JBIDE-25309 > URL: https://issues.jboss.org/browse/JBIDE-25309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, central-update > Affects Versions: 4.5.1.Final > Environment: RHEL7, OpenJDK 1.8 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png > > > I can't install stuff from RH Central into JBoss Tools because of unavailable connectors. > There is dialog I got: > !JBT_unavailable_connectors.png|thumbnail! > After click "No" the error dialog with this message was displayed: > [^JBT_unavailable_connectors.txt] > Error message is saying that some features is missing on update site \[1\] but I see that these features present on update site. I chosen one of the connectors and verified that it is possible to install them form update site using Help -> Install New Software -> Add \[1\]. > \[1\] http://download.jboss.org/jbosstools/oxygen/staging/updates/ > This problem appears only in JBoss Tools, JBDS works fine. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25309: ------------------------------------ Cannot reproduce here on F24 w/ JDK 8 in Eclipse JEE bundle 4.7.1a (Oxygen.1a). !central-451final-works-fine.png|thumbnail! > Can't install stuff from RH Central into JBoss Tools > ---------------------------------------------------- > > Key: JBIDE-25309 > URL: https://issues.jboss.org/browse/JBIDE-25309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, central-update > Affects Versions: 4.5.1.Final > Environment: RHEL7, OpenJDK 1.8 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png > > > I can't install stuff from RH Central into JBoss Tools because of unavailable connectors. > There is dialog I got: > !JBT_unavailable_connectors.png|thumbnail! > After click "No" the error dialog with this message was displayed: > [^JBT_unavailable_connectors.txt] > Error message is saying that some features is missing on update site \[1\] but I see that these features present on update site. I chosen one of the connectors and verified that it is possible to install them form update site using Help -> Install New Software -> Add \[1\]. > \[1\] http://download.jboss.org/jbosstools/oxygen/staging/updates/ > This problem appears only in JBoss Tools, JBDS works fine. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25309: ------------------------------- Attachment: central-451final-works-fine.png > Can't install stuff from RH Central into JBoss Tools > ---------------------------------------------------- > > Key: JBIDE-25309 > URL: https://issues.jboss.org/browse/JBIDE-25309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, central-update > Affects Versions: 4.5.1.Final > Environment: RHEL7, OpenJDK 1.8 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png > > > I can't install stuff from RH Central into JBoss Tools because of unavailable connectors. > There is dialog I got: > !JBT_unavailable_connectors.png|thumbnail! > After click "No" the error dialog with this message was displayed: > [^JBT_unavailable_connectors.txt] > Error message is saying that some features is missing on update site \[1\] but I see that these features present on update site. I chosen one of the connectors and verified that it is possible to install them form update site using Help -> Install New Software -> Add \[1\]. > \[1\] http://download.jboss.org/jbosstools/oxygen/staging/updates/ > This problem appears only in JBoss Tools, JBDS works fine. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25311) Use default plugin classpath in 'org.jboss.tools.hibernate.ui'

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25311?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-25311: ------------------------------ Fix Version/s: 4.5.2.AM1 > Use default plugin classpath in 'org.jboss.tools.hibernate.ui' > -------------------------------------------------------------- > > Key: JBIDE-25311 > URL: https://issues.jboss.org/browse/JBIDE-25311 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.2.AM1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25311) Use default plugin classpath in 'org.jboss.tools.hibernate.ui'

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25311?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-25311: --------------------------------- Assignee: Koen Aers > Use default plugin classpath in 'org.jboss.tools.hibernate.ui' > -------------------------------------------------------------- > > Key: JBIDE-25311 > URL: https://issues.jboss.org/browse/JBIDE-25311 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25311) Use default plugin classpath in 'org.jboss.tools.hibernate.ui'

by Koen Aers (JIRA)

Koen Aers created JBIDE-25311: --------------------------------- Summary: Use default plugin classpath in 'org.jboss.tools.hibernate.ui' Key: JBIDE-25311 URL: https://issues.jboss.org/browse/JBIDE-25311 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4392) DevTools 2.1 RPM Epic

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4392?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4392. ------------------------------ > DevTools 2.1 RPM Epic > --------------------- > > Key: JBDS-4392 > URL: https://issues.jboss.org/browse/JBDS-4392 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build, platform-installer, rhscl, rpm, target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > > Epic to track issues related to devstudio & devsuite rpm creation & publishing to devtools or RHSCL channel -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25126) Server adapter editor, -wizard: validate debug-key, debug-port-key fields

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25126?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25126. --------------------------------- Closing. Validation is working. Verified in: Red Hat JBoss Developer Studio Version: 11.1.0.GA Build id: GA-v20171026-1022-B1486 Build date: 20171026-1022 > Server adapter editor, -wizard: validate debug-key, debug-port-key fields > ------------------------------------------------------------------------- > > Key: JBIDE-25126 > URL: https://issues.jboss.org/browse/JBIDE-25126 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor, server_adapter_wizard > Fix For: 4.5.1.Final > > > Currently there's no validation (debug port is only required to be a numerical value, keys are free of any constraint) of the keys and values if they're provided. We should validate them. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25091) Edit resource limits wizard: setting memory resource limits errors if you use the 2 duplicate MiB entries

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25091?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25091: ---------------------------------- Sprint: (was: devex #140 November 2017) > Edit resource limits wizard: setting memory resource limits errors if you use the 2 duplicate MiB entries > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25091 > URL: https://issues.jboss.org/browse/JBIDE-25091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits.png, error-limit-must-be-equal-or-greater-than-request.png, image-2017-09-22-13-02-35-216.png, memory-limit-limit.png, memory-request-limit.png, request-resource-limit-combo.png, resource-limits-web-console.png, units.png > > > When editing memory settings in dialog "Edit resource limits", there is a duplicate value MiB in the Combos for Memory > "Request" and Memory > "Limit": > !edit-resource-limits.png! > You can have setting the limits error inexplicably in the following way: > # ASSERT: make sure that you have an application with a service, replication controller/deployment config running in OpenShift (ex. create one using the nodejs-mongo-persistent template) > # EXEC: in OpenShift explorer: select the service for your application and pick "Edit resource limit" in the context menu for it > # ASSERT: "Edit resource limit" dialog shows up > # EXEC: set Memory > Request to 128 and pick the 1st MiB entry in the combo > !memory-request-limit.png! > # EXEC: set Memory > Limit to 512 and pick the 2nd MiB entry in the combo > !memory-limit-limit.png! > # EXEC: "Finish" the wizard > Result: > The wizard errors telling you that the limit must be equal or greater than the request: > !error-limit-must-be-equal-or-greater-than-request.png! > In the Eclipse log you find the following: > {code} > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.64.12:8443/oapi/v1/namespaces/nodejs/deploymentconfigs/no... response code: 422 DeploymentConfig "nodejs-mongo-persistent" is invalid: spec.template.spec.containers[0].resources.limits: Invalid value: "512": must be greater than or equal to memory request > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > 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:258) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:316) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.wizard.common.EditResourceLimitsHandler$EditResourceLimitsWizard$1.run(EditResourceLimitsHandler.java:117) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25091) Edit resource limits wizard: setting memory resource limits errors if you use the 2 duplicate MiB entries

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25091?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25091. --------------------------------- Closing. labels and behavior is fixed. Verified in: Red Hat JBoss Developer Studio Version: 11.1.0.GA Build id: GA-v20171026-1022-B1486 Build date: 20171026-1022 > Edit resource limits wizard: setting memory resource limits errors if you use the 2 duplicate MiB entries > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25091 > URL: https://issues.jboss.org/browse/JBIDE-25091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits.png, error-limit-must-be-equal-or-greater-than-request.png, image-2017-09-22-13-02-35-216.png, memory-limit-limit.png, memory-request-limit.png, request-resource-limit-combo.png, resource-limits-web-console.png, units.png > > > When editing memory settings in dialog "Edit resource limits", there is a duplicate value MiB in the Combos for Memory > "Request" and Memory > "Limit": > !edit-resource-limits.png! > You can have setting the limits error inexplicably in the following way: > # ASSERT: make sure that you have an application with a service, replication controller/deployment config running in OpenShift (ex. create one using the nodejs-mongo-persistent template) > # EXEC: in OpenShift explorer: select the service for your application and pick "Edit resource limit" in the context menu for it > # ASSERT: "Edit resource limit" dialog shows up > # EXEC: set Memory > Request to 128 and pick the 1st MiB entry in the combo > !memory-request-limit.png! > # EXEC: set Memory > Limit to 512 and pick the 2nd MiB entry in the combo > !memory-limit-limit.png! > # EXEC: "Finish" the wizard > Result: > The wizard errors telling you that the limit must be equal or greater than the request: > !error-limit-must-be-equal-or-greater-than-request.png! > In the Eclipse log you find the following: > {code} > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.64.12:8443/oapi/v1/namespaces/nodejs/deploymentconfigs/no... response code: 422 DeploymentConfig "nodejs-mongo-persistent" is invalid: spec.template.spec.containers[0].resources.limits: Invalid value: "512": must be greater than or equal to memory request > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > 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:258) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:316) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.wizard.common.EditResourceLimitsHandler$EditResourceLimitsWizard$1.run(EditResourceLimitsHandler.java:117) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2017