April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25217) Integration Tests: DebuggingEAPAppTest, Win10: Eclipse is missing required privileges

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25217?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25217: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Integration Tests: DebuggingEAPAppTest, Win10: Eclipse is missing required privileges > ------------------------------------------------------------------------------------- > > Key: JBIDE-25217 > URL: https://issues.jboss.org/browse/JBIDE-25217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Environment: Windows 10 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18556) battery status is not reflected in browsersim's status bar

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18556?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18556: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > battery status is not reflected in browsersim's status bar > ---------------------------------------------------------- > > Key: JBIDE-18556 > URL: https://issues.jboss.org/browse/JBIDE-18556 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Minor > Fix For: 4.6.x > > Attachments: log.png > > > create basic cordova app. > run in cordova sim. > changing the battery level and is-plugged does not take effect in the simulator. > Should it not be able to detect these ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23264) Add content assistant for attributes restart, include, exclude, etc. in design view

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23264?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23264: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Add content assistant for attributes restart, include, exclude, etc. in design view > ----------------------------------------------------------------------------------- > > Key: JBIDE-23264 > URL: https://issues.jboss.org/browse/JBIDE-23264 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.4.1.Final > Environment: Fedora 24 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Fix For: 4.6.x > > > In general, content assist does not work in Design View (in tables, where properties, exception and other components are defined) and also in Diagram View in Properties tab. Seems that this features are not implemented yet. Also, it is missing at defining the properties (ie. in section Properties of Batchlet artefact definitionin design view tab) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25305) JPA Java Change Event Handler

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25305?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25305: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > JPA Java Change Event Handler > ----------------------------- > > Key: JBIDE-25305 > URL: https://issues.jboss.org/browse/JBIDE-25305 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: hibernate > Reporter: Anton Hughes > Assignee: Koen Aers > Fix For: 4.6.x > > > Please see: > * https://stackoverflow.com/questions/46965318/disable-jpa-java-change-even... > * https://developer.jboss.org/thread/256558 > This issue has gone on for years. Just do a google and you will find lots of people complaining about this. > Its not exclusively a problem of JBDS / Jboss tools, but these IDEs do include plugins which have had this issue for years. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23417) [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23417?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23417: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23417 > URL: https://issues.jboss.org/browse/JBIDE-23417 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, integration-test, openshift_v3 > Fix For: 4.6.x > > Attachments: services-and-routing-settings-wizard-page.png > > > We should create/add integration tests for the "Services and Routing Settings" wizard page which recently got a new column to set the port for the route added. > !services-and-routing-settings-wizard-page.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22164) Allow to create secrets for OpenShift 3 projects

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22164?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22164: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Allow to create secrets for OpenShift 3 projects > ------------------------------------------------ > > Key: JBIDE-22164 > URL: https://issues.jboss.org/browse/JBIDE-22164 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.6.x > > > Not every developer will use only public git and docker repositories. Or there are other reasons for usage of secrets. It would be nice if we would have some simple wizard to add a secret for OpenShift project/connection (would be accessible for all projects of a connection). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21350) Error importing plain java project

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21350?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21350: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Error importing plain java project > ---------------------------------- > > Key: JBIDE-21350 > URL: https://issues.jboss.org/browse/JBIDE-21350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, upstream > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1a > Reporter: Radim Hopp > Assignee: Mickael Istria > Fix For: 4.6.x > > Attachments: Easymporttestproject.tar.gz > > > Entering ImportProposalsWizardPage using directory containing plain java project (in attachment), > "No import proposal could be computed..." dialog pops up and after that an error: > {noformat:title=Problems occurred when invoking code from plug-in: "org.eclipse.jface".} > java.lang.IndexOutOfBoundsException: Index: 0 > at java.util.Collections$EmptyList.get(Collections.java:4454) > at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$ProjectConfiguratorLabelProvider.getText(ImportProposalsWizardPage.java:108) > at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$ProjectConfiguratorLabelProvider.update(ImportProposalsWizardPage.java:126) > at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:154) > at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:949) > at org.eclipse.jface.viewers.CheckboxTreeViewer.doUpdateItem(CheckboxTreeViewer.java:120) > at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:114) > 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.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1029) > at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:473) > 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.viewers.StructuredViewer.updateItem(StructuredViewer.java:2176) > at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:843) > at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:818) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791) > at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541) > at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790) > at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462) > at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423) > at org.eclipse.jface.viewers.CheckboxTreeViewer.preservingSelection(CheckboxTreeViewer.java:409) > at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517) > at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292) > at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701) > at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$7.run(ImportProposalsWizardPage.java:296) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002) > at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.updateTreeContent(ImportProposalsWizardPage.java:270) > at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.pageChanged(ImportProposalsWizardPage.java:320) > at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505) > 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.firePageChanged(WizardDialog.java:1502) > at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1234) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194) > 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.wizards.datatransfer.OpenFolderCommand.execute(OpenFolderCommand.java:91) > 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.GeneratedMethodAccessor149.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.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592) > 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:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > 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) > {noformat} > "Import as" column is empty, but clicking finish imports the project correctly (with Java and JDT natures) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24737) [jeetools] Merge jeetools and ejbtools

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24737?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24737: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > [jeetools] Merge jeetools and ejbtools > -------------------------------------- > > Key: JBIDE-24737 > URL: https://issues.jboss.org/browse/JBIDE-24737 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: Rob Stryker > Fix For: 4.6.x > > > jeetools and servertools have extensive interconnections on a plugin level. These two should be merged. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18098) many "Unknown" markers during maven import

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18098?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18098: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > many "Unknown" markers during maven import > ------------------------------------------ > > Key: JBIDE-18098 > URL: https://issues.jboss.org/browse/JBIDE-18098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.6.x > > > not sure if this is a maven or eclipse issue but when importing javaee7-samples the problem view lists *alot* of unknown markers. > example: https://www.dropbox.com/s/63n9f1kxn9ubrg7/Screenshot%202014-08-20%2012.49... > Eventually they dissapear, but they are there for several minutes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19526) JPA validation doesn't detect generator strategy file removal

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19526?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19526: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > JPA validation doesn't detect generator strategy file removal > ------------------------------------------------------------- > > Key: JBIDE-19526 > URL: https://issues.jboss.org/browse/JBIDE-19526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.CR1 > Environment: JBDS 8.1.0.CR1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.6.x > > > JPA Validator normally checks if generator strategy exist. For example when you give wrong name, it reports error which is expected. But when strategy file removed by project explorer it doesn't report any error and reports no error in project. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 2018