October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25269) add org.eclipse.lsp4e from http://download.eclipse.org/lsp4e/snapshots/ to both 4.70.x and 4.71.x TPs

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25269: ---------------------------------- Summary: add org.eclipse.lsp4e from http://download.eclipse.org/lsp4e/snapshots/ to both 4.70.x and 4.71.x TPs Key: JBIDE-25269 URL: https://issues.jboss.org/browse/JBIDE-25269 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build, fabric8, target-platform, updatesite Affects Versions: 4.5.1.Final Reporter: Nick Boldt add org.eclipse.lsp4e from http://download.eclipse.org/lsp4e/snapshots/ to both 4.70.x and 4.71.x TPs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25268) cannot deploy jbosstools-hibernate to dl.jb.o

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25268?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25268: ------------------------------- Description: {code} 15:27:49 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project hibernatetools.doc: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was: {code} 15:27:49 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project hibernatetools.doc: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] {code} > cannot deploy jbosstools-hibernate to dl.jb.o > --------------------------------------------- > > Key: JBIDE-25268 > URL: https://issues.jboss.org/browse/JBIDE-25268 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, hibernate > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > > {code} > 15:27:49 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on > project hibernatetools.doc: Deployment failed: repository element was not specified in the > POM inside distributionManagement element or in > -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25268) cannot deploy jbosstools-hibernate to dl.jb.o

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25268: ---------------------------------- Summary: cannot deploy jbosstools-hibernate to dl.jb.o Key: JBIDE-25268 URL: https://issues.jboss.org/browse/JBIDE-25268 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, hibernate Affects Versions: 4.5.1.Final Reporter: Nick Boldt Priority: Blocker {code} 15:27:49 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project hibernatetools.doc: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25268) cannot deploy jbosstools-hibernate to dl.jb.o

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25268?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25268: ---------------------------------- Assignee: Nick Boldt > cannot deploy jbosstools-hibernate to dl.jb.o > --------------------------------------------- > > Key: JBIDE-25268 > URL: https://issues.jboss.org/browse/JBIDE-25268 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, hibernate > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > > {code} > 15:27:49 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on > project hibernatetools.doc: Deployment failed: repository element was not specified in the > POM inside distributionManagement element or in > -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25268) cannot deploy jbosstools-hibernate to dl.jb.o

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25268?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25268: ------------------------------- Fix Version/s: 4.5.1.Final > cannot deploy jbosstools-hibernate to dl.jb.o > --------------------------------------------- > > Key: JBIDE-25268 > URL: https://issues.jboss.org/browse/JBIDE-25268 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, hibernate > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > > {code} > 15:27:49 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on > project hibernatetools.doc: Deployment failed: repository element was not specified in the > POM inside distributionManagement element or in > -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25092) Edit resource limits wizard: Move labels

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25092?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25092: ------------------------------------- Sprint: devex #140 November 2017 > Edit resource limits wizard: Move labels > ----------------------------------------- > > Key: JBIDE-25092 > URL: https://issues.jboss.org/browse/JBIDE-25092 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Minor > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits.png > > > Please move labels for CPU and memory a little bit up (reduce the vertical space btw. the text field & label and the upper border of the group they're in). The labels also miss the ":", which is the standard for widget labels in Eclipse. > !edit-resource-limits.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25092) Edit resource limits wizard: Move labels

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25092?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25092: ------------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) > Edit resource limits wizard: Move labels > ----------------------------------------- > > Key: JBIDE-25092 > URL: https://issues.jboss.org/browse/JBIDE-25092 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Minor > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits.png > > > Please move labels for CPU and memory a little bit up (reduce the vertical space btw. the text field & label and the upper border of the group they're in). The labels also miss the ":", which is the standard for widget labels in Eclipse. > !edit-resource-limits.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25263: ------------------------------------ [~ljelinko] Are you sure both tokens were the same because they only different by the end if I remember correctly. > OSIO Error refreshing token > --------------------------- > > Key: JBIDE-25263 > URL: https://issues.jboss.org/browse/JBIDE-25263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Lucia Jelinkova > Assignee: Jeff MAURY > Labels: OSIO > Fix For: 4.5.x > > > When I called the OSIO service from Fabric8 plugin, the following error occurred. > {code:java} > org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io > at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168) > at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101) > at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24) > at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1) > at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60) > at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67) > at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102) > at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142) > at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199) > at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163) > at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261) > at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} > Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24868: ------------------------------- Sprint: devex #138 September 2017, devex #140 November 2017 (was: devex #138 September 2017) > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.Final > > Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24868: ------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.Final > > Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2017