September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23205) Allow to lookup ReplicationController for a Service without having to get to the pods

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23205?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23205. --------------------------------- > Allow to lookup ReplicationController for a Service without having to get to the pods > ------------------------------------------------------------------------------------- > > Key: JBIDE-23205 > URL: https://issues.jboss.org/browse/JBIDE-23205 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM1 > > > When looking up a replication for a service, the current approach that we have requires us to go and get the pods that match the service we're starting with. Once we have these we then can determine what replication controller controls them. > This only works if a replication controller is set to have replicas. If there are none there are no pods and we're thus stuck. > The match can be done directly: match the labels of the pod templates within the replication controller against the service we're starting with. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Václav Kadlčík (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Václav Kadlčík commented on JBDS-4059: -------------------------------------- Let me elaborate as the original html report makes little sense outside RHEL TPS. Basically, the tool I used found several issues in references to outside shared libraries. Namely: * libraries of ORBit2, gnome-vfs2, and libIDL are referred but they aren't present on the SUT; in practice, the rh-eclipse46-devstudio RPM should require either those RPMs or their respective "Provides" * libnotify.so.1 is referred but it does not exist on RHEL 7 (but libnotify.so.4 exists) Such discrepancies can be found/verified using commands like "ldd ..." (find referred libraries, if I oversimplify) and "yum whatprovides ..." but I guess I'm stating obvious... > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21766) NPE when trying to generate mapping files on project with no console config

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21766?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-21766. ------------------------------------ verified in Devstudio 10.2.0.AM1-v20160921-0614-B6069 > NPE when trying to generate mapping files on project with no console config > --------------------------------------------------------------------------- > > Key: JBIDE-21766 > URL: https://issues.jboss.org/browse/JBIDE-21766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.2.AM1 > > > {code} > java.lang.NullPointerException > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.getService(ConfigurationActor.java:127) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfiguration(ConfigurationActor.java:134) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfigurations(ConfigurationActor.java:117) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.createConfigurations(NewHibernateMappingFileWizard.java:559) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.getPlaces2Gen(NewHibernateMappingFileWizard.java:316) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.handlePageChanging(NewHibernateMappingFileWizard.java:172) > at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1554) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1551) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:899) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1186) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885) > 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:1329) > 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$New.executeHandler(WizardHandler.java:269) > 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.GeneratedMethodAccessor106.invoke(Unknown Source) > 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:1329) > 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:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > 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} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Pavol Srna reassigned JBDS-4059: -------------------------------- Assignee: Nick Boldt > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Pavol Srna (JIRA)

Pavol Srna created JBDS-4059: -------------------------------- Summary: RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. Key: JBDS-4059 URL: https://issues.jboss.org/browse/JBDS-4059 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: build Reporter: Pavol Srna [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23110) hibernate New and Noteworthy for 4.4.1.Final

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23110?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23110. ------------------------------------ verified on website > hibernate New and Noteworthy for 4.4.1.Final > -------------------------------------------- > > Key: JBIDE-23110 > URL: https://issues.jboss.org/browse/JBIDE-23110 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Fix For: 4.4.1.Final > > > If no news for 4.4.1.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.1.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-23039: ------------------------------------------- {quote} After a last bug involving the console view stealing input from the process streams, this is fixed, tested, and committed in master. {quote} Nice. > Need an interactive terminal that fits specific requirements > ------------------------------------------------------------ > > Key: JBIDE-23039 > URL: https://issues.jboss.org/browse/JBIDE-23039 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: cdk, new_and_noteworthy > Fix For: 4.4.2.AM1 > > Attachments: vagranttty.png > > > CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. > 1) I must be able to get a Process or IProcess object when a command is run > 2) I must be able to get an event or know when the process terminates > 3) The terminal or console must be interactive and allow user input when prompted. > 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. > These three requirements thus far seem impossible to solve. Solutions that have been attempted are: > 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. > 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed: > a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input > b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen > 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. > Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. > Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? > No other obvious solutions have presented themselves in the past year. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13661) Cannot create archive from archive in explorer

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13661?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-13661: ------------------------------------------ [~rob.stryker] Im able to reproduce. Jaroslav mentions Project Archive explorer but he really means Project Explorer :) So steps are: 1. use new workspace, do NOT open Project Archives view 2. create java project 3. in Project Explorer, using right click on project, add Archives support 4. create archive using Project Explorer (name it archive.jar) 5. create archive for archive.jar in Project Explorer FAIL: Nothing happens, dialog for new archive wont open Exception happens here https://github.com/jbosstools/jbosstools-server/blob/master/archives/plug... - getInstance() returns null (bcs Project Archives View is not open) and you swallow it here https://github.com/jbosstools/jbosstools-server/blob/master/archives/plug... > Cannot create archive from archive in explorer > ---------------------------------------------- > > Key: JBIDE-13661 > URL: https://issues.jboss.org/browse/JBIDE-13661 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23211) JS Alert popups are not disabled on Windows

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-23211: ---------------------------------------- Summary: JS Alert popups are not disabled on Windows Key: JBIDE-23211 URL: https://issues.jboss.org/browse/JBIDE-23211 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core Affects Versions: 4.4.1.Final Reporter: Rastislav Wagner -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-909) Update SAPComponent test so that it uses an empty Fuse project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-909?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-909: ------------------------------------ Summary: Update SAPComponent test so that it uses an empty Fuse project (was: Update SAP tests so that we can specify the Camel version) > Update SAPComponent test so that it uses an empty Fuse project > -------------------------------------------------------------- > > Key: JBTIS-909 > URL: https://issues.jboss.org/browse/JBTIS-909 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.2.CR1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.3.2.CR1 > > > Update SAP tests so that we can specify the Camel version. Currently, it takes the default version which is 2.17.3 for which there is no the appropriated sap version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016