November 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-202) Purge or archive old JBTIS jobs that are no longer used or needed

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-202?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-202. ------------------------------ Fix Version/s: 4.1.3 Resolution: Done see comment from Nick. > Purge or archive old JBTIS jobs that are no longer used or needed > ----------------------------------------------------------------- > > Key: JBTIS-202 > URL: https://issues.jboss.org/browse/JBTIS-202 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: releng > Affects Versions: 4.1.3.Beta5 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.1.3 > > > Looking at the SOATooling view... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOAT... > these (new) jobs are blue: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... > but these older install-tests jobs are red: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOAT... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOAT... > Are they still used? > Would it be better if you had a JBTIS 4.1 version of this job, for use with Eclipse 43x instead of 42x? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOAT... > Also, are these jobs obsolete (haven't run successfully in 11mo)? Should we archive them? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOAT... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOAT... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16026) Server adapter: when using php type app, deploy project is not displayed nor changeable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16026?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16026: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have an account with a *non-jbossas/jbosseasp/ews) application in OpenShift and that your application is imported to your workspace # EXEC: Launch server adapter wizard and create a new server adapter for your application # EXEC: once it's created double click your new server adapter so that the Server Adapter editor shows up Result: The server adapter editor has the *Project* combo disabled and not showing the project that the adapter is bounds to. Pushing the adapter works but you cannot change nor see what application it is bound to (beside that it has the very same name as your workspace project and the OS application). Furthermore the remote name and deploy folder widgets should be disabled initially, should be only enabled when you check "Override Project Settings" !server-editor.png! The correct visual appearance is the following (deploy project is enabled and the correct project is selected, deploy folder and remote are disabled) !correct-server-adapter.png! was: # ASSERT: make sure that you have an account with a *non-jbossas/jbosseasp/ews) application in OpenShift and that your application is imported to your workspace # EXEC: Launch server adapter wizard and create a new server adapter for your application # EXEC: once it's created double click your new server adapter so that the Server Adapter editor shows up Result: The server adapter editor has the *Project* combo disabled and not showing the project that the adapter is bounds to. Pushing the adapter works but you cannot change nor see what application it is bound to (beside that it has the very same name as your workspace project and the OS application). Furthermore the remote name and deploy folder widgets should be disabled initially, should be only enabled when you check "Override Project Settings" !server-editor.png! > Server adapter: when using php type app, deploy project is not displayed nor changeable > --------------------------------------------------------------------------------------- > > Key: JBIDE-16026 > URL: https://issues.jboss.org/browse/JBIDE-16026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.1.CR1 > > Attachments: correct-server-adapter.png, server-editor.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16026) Server adapter: when using php type app, deploy project is not displayed nor changeable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16026?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16026: ------------------------------------- Attachment: correct-server-adapter.png > Server adapter: when using php type app, deploy project is not displayed nor changeable > --------------------------------------------------------------------------------------- > > Key: JBIDE-16026 > URL: https://issues.jboss.org/browse/JBIDE-16026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.1.CR1 > > Attachments: correct-server-adapter.png, server-editor.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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2807) Update jrebel updatesite to use separate url for install feedback

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2807?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2807 at 11/19/13 10:04 AM: ------------------------------------------------------------- Patches & PRs to fix this in the actual code (not just on the server, and bump plugin versions where needed): *JBT 3.3.x / JBDS 5.0.x* * [^JBDS2807_JBT33x_patch2.txt] {color:green}Applied{color} * [^JBDS2807_JBDS50x_patch2.txt] {color:green}Applied{color} *JBT 4.0.x / JBDS 6.0.x* * https://github.com/jbosstools/jbosstools-central/pull/184 (jbosstools-4.0.x) {color:green}Applied{color} * [^JBDS2807_JBDS60x_patch2.txt] {color:green}Applied{color} *JBT 4.1.0.x / JBDS 7.0.x* * https://github.com/jbosstools/jbosstools-discovery/pull/111 (jbosstools-4.1.0.x) {color:green}Applied{color} *JBT 4.1.x / JBDS 7.1.x* * https://github.com/jbosstools/jbosstools-discovery/pull/107 (jbosstools-4.1.x) {color:green}Applied{color} *JBT 4.2.x / JBDS 8.0.x* * https://github.com/jbosstools/jbosstools-discovery/pull/106 (master) {color:green}Applied{color} was (Author: nickboldt): Patches & PRs to fix this in the actual code (not just on the server, and bump plugin versions where needed): *JBT 3.3.x / JBDS 5.0.x* * [^JBDS2807_JBT33x_patch2.txt] {color:green}Applied{color} * [^JBDS2807_JBDS50x_patch2.txt] {color:green}Applied{color} *JBT 4.0.x / JBDS 6.0.x* * https://github.com/jbosstools/jbosstools-central/pull/184 (jbosstools-4.0.x) {color:red}Waiting...{color} * [^JBDS2807_JBDS60x_patch2.txt] {color:green}Applied{color} *JBT 4.1.0.x / JBDS 7.0.x* * https://github.com/jbosstools/jbosstools-discovery/pull/111 (jbosstools-4.1.0.x) {color:green}Applied{color} *JBT 4.1.x / JBDS 7.1.x* * https://github.com/jbosstools/jbosstools-discovery/pull/107 (jbosstools-4.1.x) {color:green}Applied{color} *JBT 4.2.x / JBDS 8.0.x* * https://github.com/jbosstools/jbosstools-discovery/pull/106 (master) {color:green}Applied{color} > Update jrebel updatesite to use separate url for install feedback > ----------------------------------------------------------------- > > Key: JBDS-2807 > URL: https://issues.jboss.org/browse/JBDS-2807 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: central, discovery > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Labels: respin-a > Fix For: 5.0.2.GA, 6.0.1.GA, 7.0.1.GA, 7.1.0.Beta1 > > Attachments: JBDS2807_after_install_JRebel.png, JBDS2807_after_install_JRebel_JBDS7beta1_b441.png, JBDS2807_JBDS502_JRebel540_installed.png, JBDS2807_JBDS50x_patch.txt, JBDS2807_JBDS50x_patch2.txt, JBDS2807_JBDS601_JRebel540_installed.png, JBDS2807_JBDS60x_patch.txt, JBDS2807_JBDS60x_patch2.txt, JBDS2807_JBDS700_JRebel540_installed.png, JBDS2807_JBT33x_patch.txt, JBDS2807_JBT33x_patch2.txt > > > jrebel would like to see how many installs central gives and have given us this special url to use in discovery.xml. > http://update.zeroturnaround.com/update-site-jboss/ > (the / at the end is important) > We should change this for all active discovery plugins that have jrebel mentioned. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15903) iOS Emulator -> iOS Simulator

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15903?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15903. ------------------------------- Verified with JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > iOS Emulator -> iOS Simulator > ----------------------------- > > Key: JBIDE-15903 > URL: https://issues.jboss.org/browse/JBIDE-15903 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Burr Sutter > Assignee: Daniel Azarov > Fix For: 4.1.1.CR1 > > Attachments: RunOnIOS.png > > > The menu label > "Run on iOS Emulator" > should be > "Run on iOS Simulator" -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15856) Android run on device command takes over run on emulator

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15856?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15856. ------------------------------- Verified with JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > Android run on device command takes over run on emulator > -------------------------------------------------------- > > Key: JBIDE-15856 > URL: https://issues.jboss.org/browse/JBIDE-15856 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.1.1.CR1 > > > If a project is ran on device once "Run on Emulator" command starts to fail or run on device if it is still connected. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15858) Env variables wizard: error when editing env variables for existing app if server does not support env variables

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15858?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15858: ------------------------------------------ This was done for 4.1.1.CR1 and 4.2.0.Alpha1 and you'll spot a warning on the top of the wizard while all widgets being disabled if env vars are not supported: !env-vars-not-supported.png! > Env variables wizard: error when editing env variables for existing app if server does not support env variables > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15858 > URL: https://issues.jboss.org/browse/JBIDE-15858 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.CR1 > > Attachments: environment_variables.png > > > If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..." > Another one is show after attempt to add variable. > Other "Processing environment variables..." > Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16032) java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16032: ------------------------------- Labels: respin-a (was: ) > java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences > --------------------------------------------------------------------- > > Key: JBIDE-16032 > URL: https://issues.jboss.org/browse/JBIDE-16032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-preferences.png > > > Stacktrace: > {code} > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$6.run(ForgeInstallationsPreferencePage.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.performOk(ForgeInstallationsPreferencePage.java:290) > at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) > at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171) > at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) > 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.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > 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.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16030) CLONE - Env variables wizard: error when editing env variables for existing app if server does not support env variables

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16030?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16030: ------------------------------------------ This was done for 4.1.1.CR1 and 4.2.0.Alpha1 and you'll spot a warning on the top of the wizard while all widgets being disabled if env vars are not supported: !env-vars-not-supported.png! > CLONE - Env variables wizard: error when editing env variables for existing app if server does not support env variables > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16030 > URL: https://issues.jboss.org/browse/JBIDE-16030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > Attachments: env-vars-not-supported.png, environment_variables.png > > > If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..." > Another one is show after attempt to add variable. > Other "Processing environment variables..." > Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16030) CLONE - Env variables wizard: error when editing env variables for existing app if server does not support env variables

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16030?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16030: ------------------------------------- Attachment: env-vars-not-supported.png > CLONE - Env variables wizard: error when editing env variables for existing app if server does not support env variables > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16030 > URL: https://issues.jboss.org/browse/JBIDE-16030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > Attachments: env-vars-not-supported.png, environment_variables.png > > > If OpenShift server does not support add/remove/modify environment variables it cause error. There should be some user-friendly dialog. See attached image. This is captured from opening shell with add/modify/remove environment variables (in context menu of application choose "Edit Environment Variables..." > Another one is show after attempt to add variable. > Other "Processing environment variables..." > Probably good solution should show dialog "Server _name_ does not support modifying environment variables" and don't open shell with table of environment variables (my opinion). -- 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, 5 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 November 2013