June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20554) Update download manager to not require country

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20554?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-20554. ------------------------------ > Update download manager to not require country > ----------------------------------------------- > > Key: JBIDE-20554 > URL: https://issues.jboss.org/browse/JBIDE-20554 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Update download-runtimes UI to either: > 1) Support version 2 of the dl-mgr rest API ORG-2524 > OR > 2) Simply wait for "Not Required" to be added as a country option ORG-2525 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22363) Connection wizard: reenable opening embedded browser for oauth token on MacOS

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22363?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22363. --------------------------------- Verified in JBoss Tools 4.4.0 nightly from 3 days ago. > Connection wizard: reenable opening embedded browser for oauth token on MacOS > ----------------------------------------------------------------------------- > > Key: JBIDE-22363 > URL: https://issues.jboss.org/browse/JBIDE-22363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: MacOS > 10.10.3 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: connection_wizard, macos, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > With JBIDE-20464, retrieving the OAuth token on OSX was done in an external browser. It seems the original bug can't be reproduced in Neon (can't select the token when opening the Connection wizard from the OpenShift explorer). So we should revert the platform specific hack, to go back to a more consistent behavior across OSes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22177) Docker Image host is missing from Deployment Config when deploying from a private registry

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22177?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22177. --------------------------------- Verified in devstudio with build id: GA-v20160602-0541-B5497 > Docker Image host is missing from Deployment Config when deploying from a private registry > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22177 > URL: https://issues.jboss.org/browse/JBIDE-22177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > > If you deploy a docker image from myregistry:5000/example/myimage, the deployment config is generated with only example/myimage, so can't find the image to deploy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22294) Build Configuration: Git Source section is cropped on OSX

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22294?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22294: --------------------------------------- I tried this with JBoss Tools 4.4.0 from a few days ago and I don't see this problem (OS X). But if I make the window smaller, then I will start losing parts of the upper part of the window - starting with the Context Directory field. So I assume that there is a default height of this window that is shown unless your desktop is too small. So this fix is an improvement - whereas before, you would always have this problem, now it's fine in most cases? > Build Configuration: Git Source section is cropped on OSX > --------------------------------------------------------- > > Key: JBIDE-22294 > URL: https://issues.jboss.org/browse/JBIDE-22294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha2 > > > After creating a new openshift application, selecting a builder image, then on the next page: > !http://content.screencast.com/users/fbricon/folders/Jing/media/5e21b5d7-9cb1-43cf-bfe9-05c1ef6e0dad/00000404.png|width=800! > Context directory field / label are cropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22294) Build Configuration: Git Source section is cropped on OSX

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22294?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22294 at 6/3/16 8:42 AM: --------------------------------------------------------------- Issue still persists in GA-v20160602-0541-B5497 if New Application Wizard is not big enough, the git source section is cropped. This is not happening only on OSX but also on Fedora 22. The Git source section should be fixed as Build Triggers section, if possible, then it should be ok. was (Author: mlabuda): Issue still persists if New Application Wizard is not big enough, the git source section is cropped. This is not happening only on OSX but also on Fedora 22. The Git source section should be fixed as Build Triggers section, if possible, then it should be ok. > Build Configuration: Git Source section is cropped on OSX > --------------------------------------------------------- > > Key: JBIDE-22294 > URL: https://issues.jboss.org/browse/JBIDE-22294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha2 > > > After creating a new openshift application, selecting a builder image, then on the next page: > !http://content.screencast.com/users/fbricon/folders/Jing/media/5e21b5d7-9cb1-43cf-bfe9-05c1ef6e0dad/00000404.png|width=800! > Context directory field / label are cropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22301) Application wizard: NPE from eclipse project with no remote git reference.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22301. --------------------------------- Verified in devstudio with build id: GA-v20160602-0541-B5497 > Application wizard: NPE 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 > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: paramter-page-invalid.png > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22169) silent runtime detection for installer eap or cdk does not work on mac

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22169?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22169. ------------------------------ Verified in Devstudio 10.0.0.GA-v20160602-0541-B5497. Closing > silent runtime detection for installer eap or cdk does not work on mac > ---------------------------------------------------------------------- > > Key: JBIDE-22169 > URL: https://issues.jboss.org/browse/JBIDE-22169 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > Attachments: jbds-tree-mac.txt > > > Today I learned that when you install jbdevstudio together with bundled eap, you should not get a popup from runtime detection when you start jbds. The bundled eap should be added silently. > This doesn't work on Mac. This is most probably because there is a different directory structure on mac. > See here: > {code} > ./runtimes > ./runtimes/jboss-eap > ./studio/jbdevstudio.app > ./studio/jbdevstudio.app/Contents > ./studio/jbdevstudio.app/Contents/Eclipse > ./studio/jbdevstudio.app/Contents/Eclipse/plugins > ./studio/jbdevstudio.app/Contents/MacOS > ./studio/jbdevstudio.app/Contents/MacOS/jbdevstudio > ./studio/jbdevstudio.app/Contents/Eclipse/configuration/ > {code} > See the attached txt for full tree. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21818) Too large margins in wizards

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21818: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Too large margins in wizards > ---------------------------- > > Key: JBIDE-21818 > URL: https://issues.jboss.org/browse/JBIDE-21818 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.x > > Attachments: Screenshot 2016-03-04 11.19.59.png > > > Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general. > See attached screenshot as an example -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] Catherine Robson commented on JBDS-3605: ---------------------------------------- [~nickboldt] is this something we can mark as resolved? > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: about-jbds10.png, Additional_RHDS_Branding.zip, edit-eap-icon-in-ds10-installer.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, new-eap-icon-in-ds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, RevisedIcons.zip, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22470) Integration tests not published to snapshots update site

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22470?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-22470: ------------------------------------ [~mmalina] Done in commit https://github.com/jbosstools/jbosstools-integration-tests/commit/6001e99... > Integration tests not published to snapshots update site > -------------------------------------------------------- > > Key: JBIDE-22470 > URL: https://issues.jboss.org/browse/JBIDE-22470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Radim Hopp > Fix For: 4.4.0.Final > > > For some reason the update site here is outdated (from March 9): > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We consume it here: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > The build is building just fine: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... > And the result is here: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... > But for some reason it's not propagated to the standard url. > Can you please check why that is? I checked the config but could not understand what's wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016