May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13891) openshift-java-client: client should not hard-code user-agent if you're usign keys

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13891?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-13891. ---------------------------------- Closing > openshift-java-client: client should not hard-code user-agent if you're usign keys > ---------------------------------------------------------------------------------- > > Key: JBIDE-13891 > URL: https://issues.jboss.org/browse/JBIDE-13891 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > > There is also very weird code in the UrlConnectionHttpClientBuilder which holds user-agent building logic. IMHO this logic should be in the rest service, not in the builder since the user-agent should get built correctly even if you create the client directly or use the builder: > {code:title=UrlConnectionHttpClientBuilder} > public IHttpClient client() { > if (authKey != null && authKey.trim().length() > 0) { > if (userAgent == null) { > userAgent = "OpenShift"; > } else if (!userAgent.startsWith("OpenShift")) { > userAgent = "OpenShift-" + userAgent; > } > } > return new UrlConnectionHttpClient(username, password, userAgent, > sslChecks, requestMediaType, acceptedMediaType, version, > authKey, authIV); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14686) ForgeWizards: Outline field in editor

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-14686: ---------------------------------- Summary: ForgeWizards: Outline field in editor Key: JBIDE-14686 URL: https://issues.jboss.org/browse/JBIDE-14686 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 4.1.0.Beta1 Reporter: Pavol Srna Fix For: 4.1.0.Beta2 New field should be outlined in editor after click on finish button in New Field Wizard. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14684) Source Lookup is triggered every time Class File Editor gets focus

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14684?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14684: -------------------------------- Description: Source Lookup is triggered every time Class File Editor gets focus. This means file identification is run *every* time, even if sources are not available. See http://screencast.com/t/fpyRi11N Also, if Class File editor was opened during last workspace shutdown, focusing on that editor will trigger file identification twice. was: Source Lookup is triggered every time Class File Editor gets focus. This means file identification is run *every* time, even if sources are not available. Also, if Class File editor was opened during last workspace shutdown, focussing on that editor will trigger file identification twice. > Source Lookup is triggered every time Class File Editor gets focus > ------------------------------------------------------------------ > > Key: JBIDE-14684 > URL: https://issues.jboss.org/browse/JBIDE-14684 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Fix For: 4.1.0.Beta2 > > > Source Lookup is triggered every time Class File Editor gets focus. > This means file identification is run *every* time, even if sources are not available. > See http://screencast.com/t/fpyRi11N > Also, if Class File editor was opened during last workspace shutdown, focusing on that editor will trigger file identification twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13021) Connection dialog: settings are to default when switching to <New Connection> but checkbox is not checked and password is erroneous

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13021?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-13021. ---------------------------------- Verified in JBoss Developer Studio 7.0.0.Beta1a > Connection dialog: settings are to default when switching to <New Connection> but checkbox is not checked and password is erroneous > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13021 > URL: https://issues.jboss.org/browse/JBIDE-13021 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta1 > > Attachments: existing-account.png, new-account.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14685) Entity file should be opened in editor after click on finish in New entity wizard

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-14685: ---------------------------------- Summary: Entity file should be opened in editor after click on finish in New entity wizard Key: JBIDE-14685 URL: https://issues.jboss.org/browse/JBIDE-14685 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.1.0.Beta1 Reporter: Pavol Srna Fix For: 4.1.0.Beta2 New entity file is correctly created, but it is not opened in editor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14683) Forge: "New.." button in Setup Persistence Wizard doesn't open New project wizard dialog

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14683?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-14683: ------------------------------- Issue Type: Bug (was: Enhancement) > Forge: "New.." button in Setup Persistence Wizard doesn't open New project wizard dialog > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14683 > URL: https://issues.jboss.org/browse/JBIDE-14683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Pavol Srna > Fix For: 4.1.0.Beta2 > > > Doesn't work in Setup Persistence and Setup Scafolding wizard. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14684) Source Lookup is triggered every time Class File Editor gets focus

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-14684: ----------------------------------- Summary: Source Lookup is triggered every time Class File Editor gets focus Key: JBIDE-14684 URL: https://issues.jboss.org/browse/JBIDE-14684 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.1.0.Beta1 Reporter: Fred Bricon Fix For: 4.1.0.Beta2 Source Lookup is triggered every time Class File Editor gets focus. This means file identification is run *every* time, even if sources are not available. Also, if Class File editor was opened during last workspace shutdown, focussing on that editor will trigger file identification twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14683) Forge: "New.." button in Setup Persistence Wizard doesn't open New project wizard dialog

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14683?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-14683: ------------------------------- Description: Doesn't work in Setup Persistence and Setup Scafolding wizard. > Forge: "New.." button in Setup Persistence Wizard doesn't open New project wizard dialog > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14683 > URL: https://issues.jboss.org/browse/JBIDE-14683 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.1.0.Beta1 > Reporter: Pavol Srna > Fix For: 4.1.0.Beta2 > > > Doesn't work in Setup Persistence and Setup Scafolding wizard. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14682) Source lookup blocks UI thread

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14682?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-14682. --------------------------------- Resolution: Done fixed with commit https://github.com/jbosstools/jbosstools-central/commit/05599773eb7987aec... > Source lookup blocks UI thread > ------------------------------ > > Key: JBIDE-14682 > URL: https://issues.jboss.org/browse/JBIDE-14682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.0.Beta2 > > > If Source lookup is active, when opening a class from a jar binary, UI freezes for a few seconds, because file identification is run in the main thread. This part should be done in a background job -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14679) Cannot create OpenShift Server Adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14679?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14679: ------------------------------------- Fix Version/s: 4.1.0.Beta2 > Cannot create OpenShift Server Adapter > -------------------------------------- > > Key: JBIDE-14679 > URL: https://issues.jboss.org/browse/JBIDE-14679 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta1 > Environment: JBoss Developer Studio 7.0.0.Beta1a > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Beta2 > > Attachments: out-1.ogv, out.ogv > > > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressServerUtils.getDefaultDeployFolder(ExpressServerUtils.java:270) > at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressServerUtils.getExpressDeployFolder(ExpressServerUtils.java:220) > at org.jboss.tools.openshift.express.internal.ui.behaviour.ExpressDetailsComposite.initModel(ExpressDetailsComposite.java:147) > at org.jboss.tools.openshift.express.internal.ui.behaviour.ExpressDetailsComposite.<init>(ExpressDetailsComposite.java:125) > at org.jboss.tools.openshift.express.internal.ui.behaviour.ExpressWizardFragment.createComposite(ExpressWizardFragment.java:62) > at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.createControl(TaskWizardPage.java:43) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1246) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) > 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.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.wst.server.ui.internal.cnf.ServersView2$1.widgetSelected(ServersView2.java:116) > 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.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416) > at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1530) > at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:361) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2079) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5430) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4569) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8707) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1243) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2287) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3361) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 May 2013