July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20222) "Create Deployment Method" gets confused when dependent is a Inner Type

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20222?page=com.atlassian.jira.plugi... ] Aslak Knutsen updated JBIDE-20222: ---------------------------------- Description: When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; * Once as the parent Type * Once as the Inner Type But it still warns that the Inner Type is not included in the Deployment. !inner_type_issue.png! In this case Type is a Enum in Target: {code} public class Target { public static enum Type { Remote, Managed, Embedded } } {code} was: When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; * Once as the parent Type * Once as the Inner Type But it still warns that the Inner Type is not included in the Deployment. In this case Type is a Enum in Target: {code} public class Target { public static enum Type { Remote, Managed, Embedded } } {code} > "Create Deployment Method" gets confused when dependent is a Inner Type > ----------------------------------------------------------------------- > > Key: JBIDE-20222 > URL: https://issues.jboss.org/browse/JBIDE-20222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Reporter: Aslak Knutsen > Attachments: inner_type_issue.png > > > When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; > * Once as the parent Type > * Once as the Inner Type > But it still warns that the Inner Type is not included in the Deployment. > !inner_type_issue.png! > In this case Type is a Enum in Target: > {code} > public class Target { > public static enum Type { > Remote, Managed, Embedded > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20222) "Create Deployment Method" gets confused when dependent is a Inner Type

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20222?page=com.atlassian.jira.plugi... ] Aslak Knutsen updated JBIDE-20222: ---------------------------------- Description: When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; * Once as the parent Type * Once as the Inner Type But it still warns that the Inner Type is not included in the Deployment. In this case Type is a Enum in Target: {code} public class Target { public static enum Type { Remote, Managed, Embedded } } {code} was: When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; * Once as the parent Type * Once as the Inner Type But it still warns that the Inner Type is not included in the Deployment. > "Create Deployment Method" gets confused when dependent is a Inner Type > ----------------------------------------------------------------------- > > Key: JBIDE-20222 > URL: https://issues.jboss.org/browse/JBIDE-20222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Reporter: Aslak Knutsen > Attachments: inner_type_issue.png > > > When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; > * Once as the parent Type > * Once as the Inner Type > But it still warns that the Inner Type is not included in the Deployment. > In this case Type is a Enum in Target: > {code} > public class Target { > public static enum Type { > Remote, Managed, Embedded > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20222) "Create Deployment Method" gets confused when dependent is a Inner Type

by Aslak Knutsen (JIRA)

Aslak Knutsen created JBIDE-20222: ------------------------------------- Summary: "Create Deployment Method" gets confused when dependent is a Inner Type Key: JBIDE-20222 URL: https://issues.jboss.org/browse/JBIDE-20222 Project: Tools (JBoss Tools) Issue Type: Bug Components: arquillian Reporter: Aslak Knutsen Attachments: inner_type_issue.png When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; * Once as the parent Type * Once as the Inner Type But it still warns that the Inner Type is not included in the Deployment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20222) "Create Deployment Method" gets confused when dependent is a Inner Type

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20222?page=com.atlassian.jira.plugi... ] Aslak Knutsen updated JBIDE-20222: ---------------------------------- Attachment: inner_type_issue.png > "Create Deployment Method" gets confused when dependent is a Inner Type > ----------------------------------------------------------------------- > > Key: JBIDE-20222 > URL: https://issues.jboss.org/browse/JBIDE-20222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Reporter: Aslak Knutsen > Attachments: inner_type_issue.png > > > When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; > * Once as the parent Type > * Once as the Inner Type > But it still warns that the Inner Type is not included in the Deployment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20221) New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20221?page=com.atlassian.jira.plugi... ] Aslak Knutsen updated JBIDE-20221: ---------------------------------- Attachment: missing_class_warnings.png > New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20221 > URL: https://issues.jboss.org/browse/JBIDE-20221 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Attachments: create_deployment_method.png, missing_class_warnings.png > > > When executing new "Arquillian JUnit Test Case" wizard and defining a "Class under test", a automatic suggestion to add 'all depending' classes should be available in the "create deployment method part". > This to avoid n number of warnings about missing classes in deployment after creation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20221) New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20221?page=com.atlassian.jira.plugi... ] Aslak Knutsen updated JBIDE-20221: ---------------------------------- Description: When executing new "Arquillian JUnit Test Case" wizard and defining a "Class under test", a automatic suggestion to add 'all depending' classes should be available in the "create deployment method part". !create_deployment_method.png! This to avoid n number of warnings about missing classes in deployment after creation. !missing_class_warnings.png! was: When executing new "Arquillian JUnit Test Case" wizard and defining a "Class under test", a automatic suggestion to add 'all depending' classes should be available in the "create deployment method part". This to avoid n number of warnings about missing classes in deployment after creation. > New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20221 > URL: https://issues.jboss.org/browse/JBIDE-20221 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Attachments: create_deployment_method.png, missing_class_warnings.png > > > When executing new "Arquillian JUnit Test Case" wizard and defining a "Class under test", a automatic suggestion to add 'all depending' classes should be available in the "create deployment method part". !create_deployment_method.png! > This to avoid n number of warnings about missing classes in deployment after creation. > !missing_class_warnings.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20221) New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20221?page=com.atlassian.jira.plugi... ] Aslak Knutsen updated JBIDE-20221: ---------------------------------- Attachment: create_deployment_method.png > New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20221 > URL: https://issues.jboss.org/browse/JBIDE-20221 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Attachments: create_deployment_method.png > > > When executing new "Arquillian JUnit Test Case" wizard and defining a "Class under test", a automatic suggestion to add 'all depending' classes should be available in the "create deployment method part". > This to avoid n number of warnings about missing classes in deployment after creation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20221) New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test

by Aslak Knutsen (JIRA)

Aslak Knutsen created JBIDE-20221: ------------------------------------- Summary: New "Arquillian Junit Test Case" wizard should have option to auto add dependent classes for class under test Key: JBIDE-20221 URL: https://issues.jboss.org/browse/JBIDE-20221 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: arquillian Reporter: Aslak Knutsen When executing new "Arquillian JUnit Test Case" wizard and defining a "Class under test", a automatic suggestion to add 'all depending' classes should be available in the "create deployment method part". This to avoid n number of warnings about missing classes in deployment after creation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20220) Arquillian Cruiser: Support Working Sets as top level

by Aslak Knutsen (JIRA)

Aslak Knutsen created JBIDE-20220: ------------------------------------- Summary: Arquillian Cruiser: Support Working Sets as top level Key: JBIDE-20220 URL: https://issues.jboss.org/browse/JBIDE-20220 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: arquillian Reporter: Aslak Knutsen Currently Cruiser will only scan current Project and children for Arquillian Test Classes. In some cases it would be useful, where multiple Project are logically bound to a single Working Set, to show all Projects within that set when current selected context is the Working Set. This would make it easy to browse all Arquillian Tests and their deployments within a multi module project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20219) Arquillian Cruiser: NPE when trying to display Deployment

by Aslak Knutsen (JIRA)

Aslak Knutsen created JBIDE-20219: ------------------------------------- Summary: Arquillian Cruiser: NPE when trying to display Deployment Key: JBIDE-20219 URL: https://issues.jboss.org/browse/JBIDE-20219 Project: Tools (JBoss Tools) Issue Type: Bug Components: arquillian Reporter: Aslak Knutsen Getting the following error when trying to view NodeTest class in Cruiser: https://github.com/arquillian/arquillian-cube/blob/master/containerless/s... {code} eclipse.buildId=4.5.0.I20150603-2000 java.version=1.8.0_45 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -data file:/home/aslak/workspace/arq_mars/ -os linux -ws gtk -arch x86_64 org.eclipse.e4.ui.workbench Error Thu Jul 09 02:52:57 CEST 2015 java.lang.NullPointerException at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getSelectedProject(ArquillianUIUtil.java:1087) at org.jboss.tools.arquillian.ui.internal.views.ArquillianView$1.selectionChanged(ArquillianView.java:90) at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:237) at org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(SelectionService.java:107) at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService.java:91) at org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(SelectionService.java:66) at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run(SelectionAggregator.java:126) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(SelectionAggregator.java:123) at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator.java:120) at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run(SelectionAggregator.java:233) at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56) at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(SelectionAggregator.java:230) at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114) at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341) at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356) at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(SelectionServiceImpl.java:31) at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(CompatibilityPart.java:441) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163) 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.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197) at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228) at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408) 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:1327) 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.views.log.EventDetailsDialog.open(EventDetailsDialog.java:181) at org.eclipse.ui.internal.views.log.EventDetailsDialogAction.run(EventDetailsDialogAction.java:98) at org.eclipse.ui.internal.views.log.LogView$15.doubleClick(LogView.java:546) at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:832) 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.fireDoubleClick(StructuredViewer.java:829) at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1470) at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1263) at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252) at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311) 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:1327) 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) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015