June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19932) v3 Application wizard, GTK3 only: Details tree shows same label everywhere

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19932?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19932: ---------------------------------------- Assignee: Andre Dietisheim > v3 Application wizard, GTK3 only: Details tree shows same label everywhere > -------------------------------------------------------------------------- > > Key: JBIDE-19932 > URL: https://issues.jboss.org/browse/JBIDE-19932 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, gtk3, upstream > Fix For: 4.3.0.Beta1 > > Attachments: same-label-for-all-items.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19932) v3 Application wizard, GTK3 only: Details tree shows same label everywhere

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19932?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19932: ------------------------------------- Attachment: same-label-for-all-items.png > v3 Application wizard, GTK3 only: Details tree shows same label everywhere > -------------------------------------------------------------------------- > > Key: JBIDE-19932 > URL: https://issues.jboss.org/browse/JBIDE-19932 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard, gtk3, upstream > Attachments: same-label-for-all-items.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19932) v3 Application wizard, GTK3 only: Details tree shows same label everywhere

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19932?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19932: ------------------------------------- Labels: application_wizard gtk3 upstream (was: ) > v3 Application wizard, GTK3 only: Details tree shows same label everywhere > -------------------------------------------------------------------------- > > Key: JBIDE-19932 > URL: https://issues.jboss.org/browse/JBIDE-19932 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard, gtk3, upstream > Attachments: same-label-for-all-items.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19932) v3 Application wizard, GTK3 only: Details tree shows same label everywhere

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19932: ---------------------------------------- Summary: v3 Application wizard, GTK3 only: Details tree shows same label everywhere Key: JBIDE-19932 URL: https://issues.jboss.org/browse/JBIDE-19932 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19931) Cannot launch v3 import wizard via File->Import->OpenShift->Existing OpenShift Application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19931?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19931: ------------------------------------- Labels: import_wizard (was: ) > Cannot launch v3 import wizard via File->Import->OpenShift->Existing OpenShift Application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19931 > URL: https://issues.jboss.org/browse/JBIDE-19931 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: import_wizard > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19931) Cannot launch v3 import wizard via File->Import->OpenShift->Existing OpenShift Application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19931?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19931: ------------------------------------- Steps to Reproduce: # EXEC: launch OpenShift import wizard via File->Import->OpenShift->Existing OpenShift Application # ASSERT: connection dialog pops up # EXEC: select or create a new v3 connection and hit "Next" Result: The connection job/progress is shown and executed but the wizard stays on the same page, doesnt get any further In the Eclipse log you'll spot the following: {code} org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a %s named %s at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:45) at org.jboss.tools.openshift.internal.ui.wizard.application.ImportApplicationWizard.init(ImportApplicationWizard.java:99) at org.jboss.tools.openshift.common.ui.wizard.AbstractApplicationWorkbenchWizard$DelegatingConnectionWizardPage.getWizard(AbstractApplicationWorkbenchWizard.java:108) at org.jboss.tools.openshift.common.ui.wizard.AbstractApplicationWorkbenchWizard$DelegatingConnectionWizardPage.getNextPage(AbstractApplicationWorkbenchWizard.java:87) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:878) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) 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:1327) 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.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) 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.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) 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:1327) 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} was: # EXEC: launch OpenShift import wizard via File->Import->OpenShift->Existing OpenShift Application # ASSERT: connection dialog pops up # EXEC: select or create a new v3 connection and hit "Next" Result: The connection job/progress is shown and executed but the wizard stays on the same page, doesnt get any further > Cannot launch v3 import wizard via File->Import->OpenShift->Existing OpenShift Application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19931 > URL: https://issues.jboss.org/browse/JBIDE-19931 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19931) Cannot launch v3 import wizard via File->Import->OpenShift->Existing OpenShift Application

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19931: ---------------------------------------- Summary: Cannot launch v3 import wizard via File->Import->OpenShift->Existing OpenShift Application Key: JBIDE-19931 URL: https://issues.jboss.org/browse/JBIDE-19931 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.3.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-3298 at 6/4/15 6:31 AM: ---------------------------------------------------------------- we went out of time for this in 9.0.0.Beta1. Postponing. was (Author: adietish): we went out of time for this in 4.3.0.Beta1. Postponing. > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3298: ----------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-19590: --------------------------------- Attachment: oomph-installer-hibernate-codebase.png > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: hibernate-psf-import.mp4, oomph-installer-hibernate-codebase.png > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015