May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22302) Outdated project examples in Help menu

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22302?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22302: ----------------------------------- Assignee: Fred Bricon > Outdated project examples in Help menu > -------------------------------------- > > Key: JBIDE-22302 > URL: https://issues.jboss.org/browse/JBIDE-22302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.1.Final > Reporter: Josef Kopriva > Assignee: Fred Bricon > Attachments: JBDS_8.0_Examples.png > > > Project examples are probably outdated in menu: *Help* >> *Project Examples...* > Repository[1] from configuration file[2] contains outdated files. > In *JBDS 9.1.0.GA* are also old sites - *8.0* - screenshot attached. > [1] http://download.jboss.org/jbosstools/examples/ > [2] http://download.jboss.org/jbosstools/configuration/ide-config.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22302) Outdated project examples in Help menu

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22302?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22302: -------------------------------- Story Points: 1 > Outdated project examples in Help menu > -------------------------------------- > > Key: JBIDE-22302 > URL: https://issues.jboss.org/browse/JBIDE-22302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.1.Final > Reporter: Josef Kopriva > Assignee: Fred Bricon > Attachments: JBDS_8.0_Examples.png > > > Project examples are probably outdated in menu: *Help* >> *Project Examples...* > Repository[1] from configuration file[2] contains outdated files. > In *JBDS 9.1.0.GA* are also old sites - *8.0* - screenshot attached. > [1] http://download.jboss.org/jbosstools/examples/ > [2] http://download.jboss.org/jbosstools/configuration/ide-config.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22301) NPE in new OS application from eclipse project with no remote git reference.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22301: ----------------------------------- Assignee: Viacheslav Kabanovich > NPE in new OS application from eclipse project with no remote git reference. > ---------------------------------------------------------------------------- > > Key: JBIDE-22301 > URL: https://issues.jboss.org/browse/JBIDE-22301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha2 > > > Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE: > {noformat:title=Unhandled event loop exception} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > 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:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > 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:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > 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:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:670) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609) > at org.eclipse.equinox.launcher.Main.run(Main.java:1516) > at org.eclipse.equinox.launcher.Main.main(Main.java:1489) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22301) NPE in new OS application from eclipse project with no remote git reference.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22301: -------------------------------- Fix Version/s: 4.4.0.Alpha2 Story Points: 2 Sprint: devex #114 May 2017 > NPE in new OS application from eclipse project with no remote git reference. > ---------------------------------------------------------------------------- > > Key: JBIDE-22301 > URL: https://issues.jboss.org/browse/JBIDE-22301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha2 > > > Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE: > {noformat:title=Unhandled event loop exception} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > 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:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > 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:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > 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:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:670) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609) > at org.eclipse.equinox.launcher.Main.run(Main.java:1516) > at org.eclipse.equinox.launcher.Main.main(Main.java:1489) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22303: ------------------------------------- [~adietish] is implementing tests for the server wizard (JBIDE-22268). We gotta make sure this one gets covered too > Server Adapter: Manually set pod deployment path is ignored > ----------------------------------------------------------- > > Key: JBIDE-22303 > URL: https://issues.jboss.org/browse/JBIDE-22303 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > > When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22303 at 5/4/16 5:05 PM: ----------------------------------------------------------------------- And, yes, method ServerSettingsWizardPageModel.update() does not make use of parameter podPath at all! When did we lose assigning the parameter to the model field? was (Author: scabanovich): And, yes, method ServerSettingsWizardPageModel.update() does not make use of parameter podPath at all! When did we loose assigning the parameter to the model field? > Server Adapter: Manually set pod deployment path is ignored > ----------------------------------------------------------- > > Key: JBIDE-22303 > URL: https://issues.jboss.org/browse/JBIDE-22303 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > > When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22303: ----------------------------------------------- And, yes, method ServerSettingsWizardPageModel.update() does not make use of parameter podPath at all! When did we loose assigning the parameter to the model field? > Server Adapter: Manually set pod deployment path is ignored > ----------------------------------------------------------- > > Key: JBIDE-22303 > URL: https://issues.jboss.org/browse/JBIDE-22303 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > > When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22300) Application Wizard: Context dir and ref are ignored in builder images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22300?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22300: -------------------------------- Story Points: 4 Sprint: devex #114 May 2017 > Application Wizard: Context dir and ref are ignored in builder images > --------------------------------------------------------------------- > > Key: JBIDE-22300 > URL: https://issues.jboss.org/browse/JBIDE-22300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Blocker > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When creating MSA application based on eap 6.4 builder image with git repo https://github.com/redhat-helloworld-msa/hello and context dir empty and ref master, the new build configuration is created wrong. Although it contains correct git repo, the ref and context dir are still pointing to old values (6.4.x and kitchensink - default in the wizard). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22300) Application Wizard: Context dir and ref are ignored in builder images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22300?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22300: ----------------------------------- Assignee: Jeff Cantrill > Application Wizard: Context dir and ref are ignored in builder images > --------------------------------------------------------------------- > > Key: JBIDE-22300 > URL: https://issues.jboss.org/browse/JBIDE-22300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Blocker > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When creating MSA application based on eap 6.4 builder image with git repo https://github.com/redhat-helloworld-msa/hello and context dir empty and ref master, the new build configuration is created wrong. Although it contains correct git repo, the ref and context dir are still pointing to old values (6.4.x and kitchensink - default in the wizard). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22300) Application Wizard: Context dir and ref are ignored in builder images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22300?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22300: -------------------------------- Fix Version/s: 4.4.0.Alpha2 > Application Wizard: Context dir and ref are ignored in builder images > --------------------------------------------------------------------- > > Key: JBIDE-22300 > URL: https://issues.jboss.org/browse/JBIDE-22300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Blocker > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When creating MSA application based on eap 6.4 builder image with git repo https://github.com/redhat-helloworld-msa/hello and context dir empty and ref master, the new build configuration is created wrong. Although it contains correct git repo, the ref and context dir are still pointing to old values (6.4.x and kitchensink - default in the wizard). -- 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 May 2016