October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-549) java.lang.Boolean - not just

by Len DiMaggio (JIRA)

Len DiMaggio created TOOLSDOC-549: ------------------------------------- Summary: java.lang.Boolean - not just Key: TOOLSDOC-549 URL: https://issues.jboss.org/browse/TOOLSDOC-549 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Environment: Build Name: 22960, Start Developing-8.0 Build Date: 22-10-2014 11:29:36 Topic ID: 13791-717241 [Latest] Reporter: Len DiMaggio Assignee: Michelle Murray Priority: Blocker Title: Add an Entity Using Forge Tools Describe the issue: The text reads: Repeat steps 5 and 6 to create three more fields for the Event entity as follows: description, with Field Type String and Length 1000 major, with Field Type Boolean We should change this so that the type to be used is: java.lang.Boolean Thx! Suggestions for improvement: Additional information: -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-549) java.lang.Boolean - not just "boolean"

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-549?page=com.atlassian.jira.plug... ] Len DiMaggio updated TOOLSDOC-549: ---------------------------------- Summary: java.lang.Boolean - not just "boolean" (was: java.lang.Boolean - not just ) > java.lang.Boolean - not just "boolean" > -------------------------------------- > > Key: TOOLSDOC-549 > URL: https://issues.jboss.org/browse/TOOLSDOC-549 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Environment: Build Name: 22960, Start Developing-8.0 > Build Date: 22-10-2014 11:29:36 > Topic ID: 13791-717241 [Latest] > Reporter: Len DiMaggio > Assignee: Michelle Murray > Priority: Blocker > > Title: Add an Entity Using Forge Tools > Describe the issue: > The text reads: > Repeat steps 5 and 6 to create three more fields for the Event entity as follows: > description, with Field Type String and Length 1000 > major, with Field Type Boolean > We should change this so that the type to be used is: > java.lang.Boolean > Thx! > Suggestions for improvement: > Additional information: -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18691) NPE while deleting a project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18691?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-18691. ---------------------------------- Resolution: Duplicate Issue > NPE while deleting a project > ---------------------------- > > Key: JBIDE-18691 > URL: https://issues.jboss.org/browse/JBIDE-18691 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha1 > > > {code} > java.lang.NullPointerException > at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:421) > at org.jboss.tools.jst.web.ui.navigator.XContentProvider.hasChildren(XContentProvider.java:96) > at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.hasChildren(SafeDelegateTreeContentProvider.java:110) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.callNormalHasChildren(NavigatorContentServiceContentProvider.java:430) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$4(NavigatorContentServiceContentProvider.java:425) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$3.run(NavigatorContentServiceContentProvider.java:395) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:381) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:422) > at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2133) > at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:553) > at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2171) > at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2863) > at org.eclipse.jface.viewers.TreeViewer.updatePlus(TreeViewer.java:804) > at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2751) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1918) > at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:684) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1893) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1850) > at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561) > at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1528) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1436) > at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1397) > at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1525) > at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:533) > at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:350) > at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:510) > at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider$1.run(JEE5ContentProvider.java:145) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:175) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:390) > at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331) > at org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:637) > at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.performFinish(UserInputWizardPage.java:153) > at org.eclipse.ltk.ui.refactoring.resource.DeleteResourcesWizard$DeleteResourcesRefactoringConfigurationPage.performFinish(DeleteResourcesWizard.java:202) > at org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:710) > at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.okPressed(RefactoringWizardDialog2.java:455) > at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466) > 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:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:187) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:202) > at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:122) > at org.eclipse.ltk.internal.ui.refactoring.actions.DeleteResourcesHandler.execute(DeleteResourcesHandler.java:40) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommandInContext(LegacyHandlerService.java:396) > at org.eclipse.ui.internal.ide.actions.LTKLauncher.runCommand(LTKLauncher.java:95) > at org.eclipse.ui.internal.ide.actions.LTKLauncher.openDeleteWizard(LTKLauncher.java:47) > at org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:474) > at org.eclipse.jdt.internal.ui.refactoring.reorg.DeleteAction.run(DeleteAction.java:197) > at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275) > at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:519) > 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:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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: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:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18592) EL code completion not working automatically with @Named with Java EE 7

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18592?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18592: -------------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) > EL code completion not working automatically with @Named with Java EE 7 > ----------------------------------------------------------------------- > > Key: JBIDE-18592 > URL: https://issues.jboss.org/browse/JBIDE-18592 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Affects Versions: 4.2.0.CR2 > Reporter: Arun Gupta > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > - Create a Dynamic Web Project > - Add the following interface: > {code} > public interface Greeting { > public String sayHello(); > } > {code} > - And the implementation: > {code} > @Dependent > @Named > public class SimpleGreeting implements Greeting { > @Override > public String sayHello() { > // TODO Auto-generated method stub > return "Hello"; > } > } > {code} > - Enable JSF facet > - Create .xhtml page as: > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html"> > <h:head></h:head> > <body> > <h:outputText value="#{}" /> > </body> > </html> > {code} > No code completion in #{}. Changing @Named to @ManagedBean works. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18694) EL code completion not working automatically with @Named with Java EE 7

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18694?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18694: ----------------------------------- Fix Version/s: (was: 4.3.0.Alpha1) > EL code completion not working automatically with @Named with Java EE 7 > ----------------------------------------------------------------------- > > Key: JBIDE-18694 > URL: https://issues.jboss.org/browse/JBIDE-18694 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Affects Versions: 4.2.0.CR2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.1.Final > > > - Create a Dynamic Web Project > - Add the following interface: > {code} > public interface Greeting { > public String sayHello(); > } > {code} > - And the implementation: > {code} > @Dependent > @Named > public class SimpleGreeting implements Greeting { > @Override > public String sayHello() { > // TODO Auto-generated method stub > return "Hello"; > } > } > {code} > - Enable JSF facet > - Create .xhtml page as: > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html"> > <h:head></h:head> > <body> > <h:outputText value="#{}" /> > </body> > </html> > {code} > No code completion in #{}. Changing @Named to @ManagedBean works. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18592) EL code completion not working automatically with @Named with Java EE 7

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18592?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18592: ----------------------------------- Fix Version/s: (was: 4.2.1.Final) > EL code completion not working automatically with @Named with Java EE 7 > ----------------------------------------------------------------------- > > Key: JBIDE-18592 > URL: https://issues.jboss.org/browse/JBIDE-18592 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Affects Versions: 4.2.0.CR2 > Reporter: Arun Gupta > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > - Create a Dynamic Web Project > - Add the following interface: > {code} > public interface Greeting { > public String sayHello(); > } > {code} > - And the implementation: > {code} > @Dependent > @Named > public class SimpleGreeting implements Greeting { > @Override > public String sayHello() { > // TODO Auto-generated method stub > return "Hello"; > } > } > {code} > - Enable JSF facet > - Create .xhtml page as: > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html"> > <h:head></h:head> > <body> > <h:outputText value="#{}" /> > </body> > </html> > {code} > No code completion in #{}. Changing @Named to @ManagedBean works. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18694) EL code completion not working automatically with @Named with Java EE 7

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-18694: -------------------------------------- Summary: EL code completion not working automatically with @Named with Java EE 7 Key: JBIDE-18694 URL: https://issues.jboss.org/browse/JBIDE-18694 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi Affects Versions: 4.2.0.CR2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.1.Final, 4.3.0.Alpha1 - Create a Dynamic Web Project - Add the following interface: {code} public interface Greeting { public String sayHello(); } {code} - And the implementation: {code} @Dependent @Named public class SimpleGreeting implements Greeting { @Override public String sayHello() { // TODO Auto-generated method stub return "Hello"; } } {code} - Enable JSF facet - Create .xhtml page as: {code} <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"> <h:head></h:head> <body> <h:outputText value="#{}" /> </body> </html> {code} No code completion in #{}. Changing @Named to @ManagedBean works. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18693) CDI validation: Don't warn if CDI 1.1 project doesn't have beans.xml

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-18693: -------------------------------------- Summary: CDI validation: Don't warn if CDI 1.1 project doesn't have beans.xml Key: JBIDE-18693 URL: https://issues.jboss.org/browse/JBIDE-18693 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.2.0.Final Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.1.Final, 4.3.0.Alpha1 1. Create a CDI 1.1 project (the project should have CDI 1.1 jars in its classpath, from WildFly 8.0 for example) 2. Don't create beans.xml file when using New CDI Web Project wizard or remove the file from the created project 3. See Problems view: "Missing beans.xml file in the project cdiweb. This file is required for bean archives [JSR-299 §12.1]" This warning message should appear only for CDI 1.0 projects. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3194) Do not see the JBoss Developer Studio Integration Stack in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3194?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3194: ---------------------------------- The JBDS IS content is not yet available in 8.0.0.GA via Central because it's only an alpha release. Once it hits beta, it will become available. Note too that it will only be available via the new Early Access program from within Central. You need to enable Early Access content to see the Integration Stack content since (again) it's still pre-release tooling, not yet at GA. Once it goes GA, it will move from Central's Early Access to its core list of available features/updates. cc: [~pleacu] > Do not see the JBoss Developer Studio Integration Stack in JBoss Central > ------------------------------------------------------------------------ > > Key: JBDS-3194 > URL: https://issues.jboss.org/browse/JBDS-3194 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: integration > Environment: F20 > Reporter: Frederic Hornain > Priority: Critical > > Well, I try to install JBoss Developer Studio Integration Stack. > However, I can not install it cause I do not see it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18597) when using 'server' keyword in New Wizard and "Tern" shows up

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18597?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-18597: ----------------------------------------- There are two Wizards defined in tern.eclipse.ide.tools.ui plug-in: "JSON type definition" and "Server Plugin" in category named "Tern". As such, when filtering by any word of "json", "type", "definition", "server", "plugin" you're getting the "Tern" category shown in the New Wizard's dialog. For some reason, the wizards themselves aren't shown though. > when using 'server' keyword in New Wizard and "Tern" shows up > -------------------------------------------------------------- > > Key: JBIDE-18597 > URL: https://issues.jboss.org/browse/JBIDE-18597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > EXECUTE: File > New > EXECUTE: Type "server" in keyword. > ASSERT: things non-related to server should not show up - like Tern. > FAILURE: Tern shows up > > See > https://www.dropbox.com/s/b3ecwm6ok1um0ab/Screenshot%202014-10-13%2015.02... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 October 2014