April 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13891?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13891: ------------------------------------- Fix Version/s: 4.1.0.Beta1 (was: 4.1.x) > 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13937) BrowserSim: syncronized devices changes after changing devices list

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-13937: ---------------------------------------------- Summary: BrowserSim: syncronized devices changes after changing devices list Key: JBIDE-13937 URL: https://issues.jboss.org/browse/JBIDE-13937 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 4.1.0.Alpha2 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.1.0.Alpha2 -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10207) Add support for JAX-RS Providers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10207?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-10207: --------------------------------------- Removig the "New and Noteworthy" label since this issue does not bring any extra visual element in the UI, nor any extra Validation / Content Assist. Yet, the work done here will be used for upcoming features. > Add support for JAX-RS Providers > -------------------------------- > > Key: JBIDE-10207 > URL: https://issues.jboss.org/browse/JBIDE-10207 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Webservices > Affects Versions: 3.3.0.M4 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > Add support for JAX-RS @Provider elements -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13936) Support deployment on multiple applications (eg: test vs prod)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13936?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13936: --------------------------------------------- I believe the server adapter today internally have code to handle overrides of which remote to push to. Thus it can push to "production", but its openshift operations would still be running against the project settings. Maybe just allow all those settings to be overridden ? > Support deployment on multiple applications (eg: test vs prod) > --------------------------------------------------------------- > > Key: JBIDE-13936 > URL: https://issues.jboss.org/browse/JBIDE-13936 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > could we support multiple platforms and have a workflow of the following kind: > 1 - user deploys to a 'test' platform/application > 2 - user tests/check it's all good > 3 - if so, he can deploy on the 'production' platform/application > This would mean, for example, having 2 server adapters and being able to support 2 'git remotes' -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10207) Add support for JAX-RS Providers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10207?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-10207: ---------------------------------- Labels: (was: new_and_noteworthy) > Add support for JAX-RS Providers > -------------------------------- > > Key: JBIDE-10207 > URL: https://issues.jboss.org/browse/JBIDE-10207 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Webservices > Affects Versions: 3.3.0.M4 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Add support for JAX-RS @Provider elements -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10207) Add support for JAX-RS Providers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10207?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-10207: ---------------------------------- Priority: Major (was: Minor) > Add support for JAX-RS Providers > -------------------------------- > > Key: JBIDE-10207 > URL: https://issues.jboss.org/browse/JBIDE-10207 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Webservices > Affects Versions: 3.3.0.M4 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Alpha2 > > > Add support for JAX-RS @Provider elements -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13936) Support deployment on multiple applications (eg: test vs prod)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13936?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-13936: ---------------------------------- Summary: Support deployment on multiple applications (eg: test vs prod) (was: Support deployment on multiple applications (test/prod) ) > Support deployment on multiple applications (eg: test vs prod) > --------------------------------------------------------------- > > Key: JBIDE-13936 > URL: https://issues.jboss.org/browse/JBIDE-13936 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > could we support multiple platforms and have a workflow of the following kind: > 1 - user deploys to a 'test' platform/application > 2 - user tests/check it's all good > 3 - if so, he can deploy on the 'production' platform/application > This would mean, for example, having 2 server adapters and being able to support 2 'git remotes' -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13936) Support deployment on multiple applications (eg: test vs prod)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13936?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-13936: ---------------------------------- Affects Version/s: 4.1.0.Alpha2 > Support deployment on multiple applications (eg: test vs prod) > --------------------------------------------------------------- > > Key: JBIDE-13936 > URL: https://issues.jboss.org/browse/JBIDE-13936 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > > could we support multiple platforms and have a workflow of the following kind: > 1 - user deploys to a 'test' platform/application > 2 - user tests/check it's all good > 3 - if so, he can deploy on the 'production' platform/application > This would mean, for example, having 2 server adapters and being able to support 2 'git remotes' -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13936) Support deployment on multiple applications (test/prod)

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-13936: ------------------------------------- Summary: Support deployment on multiple applications (test/prod) Key: JBIDE-13936 URL: https://issues.jboss.org/browse/JBIDE-13936 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Xavier Coulon Assignee: Andre Dietisheim could we support multiple platforms and have a workflow of the following kind: 1 - user deploys to a 'test' platform/application 2 - user tests/check it's all good 3 - if so, he can deploy on the 'production' platform/application This would mean, for example, having 2 server adapters and being able to support 2 'git remotes' -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13856: --------------------------------------------- do you have a PR I can look at ? > Test jQuery Mobile Palette Wizards on different platforms > --------------------------------------------------------- > > Key: JBIDE-13856 > URL: https://issues.jboss.org/browse/JBIDE-13856 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Fix For: 4.1.0.Alpha2 > > Attachments: jbide-13856.patch, ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png > > > If system font size is set to large, wizard should take it into account. > For instance: > !ubuntu_64_large_font_toggle.png! > Windows 8 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari: > jQuery Mobile Palette Widget Wizards work fine. > Windows 8 64bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari: > Wizards do not start > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]) > at org.eclipse.swt.SWT.error(SWT.java:4373) > at org.eclipse.swt.SWT.error(SWT.java:4288) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > 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(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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) > Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser] > at org.eclipse.swt.SWT.error(SWT.java:4399) > at org.eclipse.swt.browser.WebKit.create(WebKit.java:542) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:99) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139) > at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) > at org.eclipse.jface.window.Window.create(Window.java:431) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) > at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95) > at org.eclipse.jface.window.Window.open(Window.java:790) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110) > at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 24 more > {code} > Windows 8 32 and 64 bits (Eclipse+Java) Base+JST + Safari: > jQuery Mobile Palette Widget Wizards work without JavaScript. > Windows 7 32 and 64 bits (Eclipse+Java) Base+JST + Safari: > jQuery Mobile Palette Widget Wizards work without JavaScript. > Windows 7 32 and 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner: > jQuery Mobile Palette Widget Wizards work fine. > Windows 7 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari: > jQuery Mobile Palette Widget Wizards work fine. > Windows 7 32 and 64 bits (Eclipse+Java) Base+JST: > Wizards do not start > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]) > at org.eclipse.swt.SWT.error(SWT.java:4392) > at org.eclipse.swt.SWT.error(SWT.java:4307) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > 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) > Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser] > at org.eclipse.swt.SWT.error(SWT.java:4418) > at org.eclipse.swt.browser.WebKit.create(WebKit.java:542) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:99) > at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139) > at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) > at org.eclipse.jface.window.Window.create(Window.java:432) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) > at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95) > at org.eclipse.jface.window.Window.open(Window.java:791) > at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110) > at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 24 more > {code} > MacOs 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner: > and > MacOs 64 bit (Eclipse+Java) Base+JST: > jQuery Mobile Palette Widget Wizards work fine. -- 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

13 years, 4 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 2013