April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22263) Reset button on Deployment Configuration wizard page in Deploy Image to OpenShift wizard could reset all env. vars

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22263: ------------------------------------- Summary: Reset button on Deployment Configuration wizard page in Deploy Image to OpenShift wizard could reset all env. vars Key: JBIDE-22263 URL: https://issues.jboss.org/browse/JBIDE-22263 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22248: --------------------------------------- >From David Hladký in https://engineering.redhat.com/rt/Ticket/Display.html?id=401756 : {quote} there is a temporary workaround - using alternative deployment domain origin-repository.jboss.org (altSnapshotDeploymentRepository switch). In the meantime we will try to find the problem with the load balancer. {quote} > Some CI jobs fail at deploying to Nexus > --------------------------------------- > > Key: JBIDE-22248 > URL: https://issues.jboss.org/browse/JBIDE-22248 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Nick, can you take a look why mvn deploy fails here? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > It worked for us in the past. > It says: > {code} > [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 04:49 min > [INFO] Finished at: 2016-04-26T09:42:02-04:00 > [INFO] Final Memory: 19M/612M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > {code} > I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team? > Cc: [~rawagner] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21218) Allow a user to add environment variables in deploy image wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21218?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21218. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Allow a user to add environment variables in deploy image wizard > ---------------------------------------------------------------- > > Key: JBIDE-21218 > URL: https://issues.jboss.org/browse/JBIDE-21218 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.4.0.Alpha1 > > > Allow a user to add and remove(the ones they added) environment variables to their deployment. We should consider also refactoring the env section of the deployment config to only declare modified values since the non-modified once are set to the same as what is expressed by the image. > * Also only remove those which were added > * Only reset those which are defaults > * Edit via double click -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21216) Improve BaseExplorerContentProvider.loadChildren()

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21216?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21216. --------------------------------- > Improve BaseExplorerContentProvider.loadChildren() > -------------------------------------------------- > > Key: JBIDE-21216 > URL: https://issues.jboss.org/browse/JBIDE-21216 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: performance > Fix For: 4.4.0.Alpha1 > > > This method may be called concurrently while children for current parentElement are being loaded. Now for this case implementation calls directly getChildrenFor(parentElement) which loads children in ui thread. So, if by some reason loading children in a separate job took a lot of time, by the same reason this second call in ui thread may hang Eclipse for some time. > Instead, it seams reasonable just to return the available loading stub as a child, when loading job is completed it will call refresh. > [~adietish] please take a look at the pull request. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21217) Unhandled loop event exception is thrown if local template file path contains invalid value

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21217?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21217. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Unhandled loop event exception is thrown if local template file path contains invalid value > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21217 > URL: https://issues.jboss.org/browse/JBIDE-21217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > In New OpenShift Application wizard while Local template tab is selected on first wizard page and if in text widget for a file is invalid value, click on a File system... button throws following exception and nothing happens: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage$14.createFileDialog(TemplateListPage.java:712) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage$14.widgetSelected(TemplateListPage.java:702) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:279) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:37) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > {code} > I expect value should be ignored and file browser dialog should be opened to allow user choose template. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21102) OpenShift Explorer: Build/Pod activity should be refreshed automatically

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21102?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21102. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > OpenShift Explorer: Build/Pod activity should be refreshed automatically > ------------------------------------------------------------------------ > > Key: JBIDE-21102 > URL: https://issues.jboss.org/browse/JBIDE-21102 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > > Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes. > We need to be able to let the explorer "watch" some specific project events (via websockets or some other method). > As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3849: -------------------------------- Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu... (was: https://github.com/redhat-developer-tooling/developer-platform-install/pu...) > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3849: ----------------------------------- Assignee: Denis Golovin (was: Nick Boldt) > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3849: -------------------------------- > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3849: -------------------------------- > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- 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