December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21202?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21202: ---------------------------------------- Priority: Blocker (was: Major) > Central is stuck on "Loading JBoss Central" when offline > -------------------------------------------------------- > > Key: JBIDE-21202 > URL: https://issues.jboss.org/browse/JBIDE-21202 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169 > Reporter: Radim Hopp > Priority: Blocker > > When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up: > {noformat} > Unable to open /resources/jbosstools-central-webpage.zip > Can't find embedded central zip > {noformat} > even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system. > In JBDS 9.0.0.GA Central can be loaded without issues when offline. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21201) TernError: No type found at the given position.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21201?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21201: ----------------------------------- Fix Version/s: 4.3.1.Beta2 4.4.0.Alpha1 (was: 4.3.0.Beta1) > TernError: No type found at the given position. > ----------------------------------------------- > > Key: JBIDE-21201 > URL: https://issues.jboss.org/browse/JBIDE-21201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript > Affects Versions: 4.3.0.Beta1 > Environment: tern 1.1.0 > Reporter: Pavol Srna > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > 1. Create JSF 1.2 Kick Start project > 2. Open inputUserName.jsp in VPE > 3. Click on 'user' text within <h:inputText> tag > 4. Press F3 key > {code} > tern.TernException: TernError: No type found at the given position. > at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) > at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) > ... 2 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-535) Missing SwitchYard tooling in JBDS-IS 8.0.4.GA on marketplace

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-535?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-535. ------------------------------ Fix Version/s: 8.0.4.GA Resolution: Done Enabled SOA tooling (com.jboss.devstudio.integration-stack.soa.feature) in Eclipse Marketplace. SwitchYard is now available. > Missing SwitchYard tooling in JBDS-IS 8.0.4.GA on marketplace > ------------------------------------------------------------- > > Key: JBTIS-535 > URL: https://issues.jboss.org/browse/JBTIS-535 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.4.CR3 > Environment: Eclipse Luna for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.4.GA > > > There is no category for installing SwitchYard tooling from Eclipse Marketplace -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-21202: ---------------------------------- Summary: Central is stuck on "Loading JBoss Central" when offline Key: JBIDE-21202 URL: https://issues.jboss.org/browse/JBIDE-21202 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.1.Beta1 Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169 Reporter: Radim Hopp When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up: {noformat} Unable to open /resources/jbosstools-central-webpage.zip Can't find embedded central zip {noformat} even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system. In JBDS 9.0.0.GA Central can be loaded without issues when offline. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21199) AssertionFailedException invoking menu on a server.

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21199?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21199: ----------------------------------------------- Server keeps runtime id, and has protected method resolve() that finds runtime object by id. There is a way to invoke it on all servers: {code} ResourceManager.getInstance().resolveServers(); {code} An IRuntimeLifecycleListener could just call it as a job on any change to runtimes. We have org.jboss.ide.eclipse.as.ui.actions.ServerManager that tracks changes to runtimes and servers. It might start such a job. The same problem takes place with project property 'Targeted Runtimes', which makes renaming Runtime in preferences a really messy thing. I wonder why wtp servertools failed to do necessary updates in workspace at changes to runtimes. > AssertionFailedException invoking menu on a server. > --------------------------------------------------- > > Key: JBIDE-21199 > URL: https://issues.jboss.org/browse/JBIDE-21199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > 1. Create a server with a JBoss runtime. > 2. Make sure that context menu is invoked without exceptions. > 3. Open Preferences/Server/Runtime Environments and rename the runtime environment bound to the server. > 4. Invoke contex menu. > Menu is opened, but there is logged exception: > {code} > !ENTRY org.eclipse.ui.navigator 4 2 2015-12-07 14:45:35.604 > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator". > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: null argument: > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) > at org.eclipse.core.runtime.Path.initialize(Path.java:641) > at org.eclipse.core.runtime.Path.<init>(Path.java:238) > at org.eclipse.core.runtime.Path.<init>(Path.java:186) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.makeRelative(LocalDeploymentOptionsController.java:44) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getDeployFolder(LocalDeploymentOptionsController.java:68) > at org.jboss.tools.as.core.server.controllable.systems.AbstractJBossDeploymentOptionsController.getDeploymentsRootFolder(AbstractJBossDeploymentOptionsController.java:78) > at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getPath(LocalExploreBehavior.java:105) > at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getDeployDirectory(LocalExploreBehavior.java:62) > at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExploreServer(LocalExploreBehavior.java:81) > at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExplore(LocalExploreBehavior.java:34) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:102) > at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219) > at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174) > at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267) > at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283) > at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333) > at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466) > at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461) > at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) > 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.Widget.sendEvent(Widget.java:1351) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1332) > at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198) > at org.eclipse.swt.widgets.Display.runPopups(Display.java:3861) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420) > 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} > I think we should prevent that exception. > 5. Open the server in editor. Its 'Runtime Environment' is empty, which means that server lost connection to the renamed environment. Can we do something to prevent it, or is it an upstream issue, or is it an expected behavior? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21189) composite install jobs now depends on early access site (thanks to angular JS requirement)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21189?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-21189. ---------------------------------- > composite install jobs now depends on early access site (thanks to angular JS requirement) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21189 > URL: https://issues.jboss.org/browse/JBIDE-21189 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, jsp/jsf/xml/html-source-editing, updatesite, upstream > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Recently, jbosstools-jst was updated to depend on a version of angularJS which is only available in our EA site, and therefore installation from the composite site fails unless we add that URL when installing. > {code} > [p2.dir] Cannot complete the install because one or more required items could not be found. > [p2.dir] Software being installed: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61) > [p2.dir] Missing requirement: Tests Plug-in 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.angularjs.test 3.7.1.Beta1-v20151204-1915-B61) requires 'bundle org.eclipse.angularjs.core 1.1.0' but it could not be found > [p2.dir] Cannot satisfy dependency: > [p2.dir] From: JBoss Tools Java Standard Tools Tests 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.feature.group 3.7.1.Beta1-v20151204-1915-B61) > [p2.dir] To: org.jboss.tools.jst.angularjs.test [3.7.1.Beta1-v20151204-1915-B61] > [p2.dir] Cannot satisfy dependency: > [p2.dir] From: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61) > [p2.dir] To: org.jboss.tools.jst.test.feature.feature.group [3.7.1.Beta1-v20151204-1915-B61] > [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_4.3.mars/eclipse/configuration/1449257171806.log > [p2.dir] Installation failed. > [p2.dir] !SESSION 2015-12-04 14:26:11.552 ----------------------------------------------- > [p2.dir] eclipse.buildId=4.5.1.M20150904-0015 > -- > [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found. > [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.880 > [p2.dir] !MESSAGE Software being installed: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61) > [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881 > [p2.dir] !MESSAGE Missing requirement: Tests Plug-in 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.angularjs.test 3.7.1.Beta1-v20151204-1915-B61) requires 'bundle org.eclipse.angularjs.core 1.1.0' but it could not be found > [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2015-12-04 14:27:05.881 > [p2.dir] !MESSAGE Cannot satisfy dependency: > [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881 > [p2.dir] !MESSAGE From: JBoss Tools Java Standard Tools Tests 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.feature.group 3.7.1.Beta1-v20151204-1915-B61) > -- > [p2.dir] !MESSAGE Cannot satisfy dependency: > [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881 > [p2.dir] !MESSAGE From: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-535) Missing SwitchYard tooling in JBDS-IS 8.0.4.GA on marketplace

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-535: --------------------------------------- Summary: Missing SwitchYard tooling in JBDS-IS 8.0.4.GA on marketplace Key: JBTIS-535 URL: https://issues.jboss.org/browse/JBTIS-535 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.4.CR3 Environment: Eclipse Luna for JEE Developers Reporter: Andrej Podhradsky Priority: Blocker There is no category for installing SwitchYard tooling from Eclipse Marketplace -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-535) Missing SwitchYard tooling in JBDS-IS 8.0.4.GA on marketplace

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-535?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky reassigned JBTIS-535: --------------------------------------- Assignee: Paul Leacu > Missing SwitchYard tooling in JBDS-IS 8.0.4.GA on marketplace > ------------------------------------------------------------- > > Key: JBTIS-535 > URL: https://issues.jboss.org/browse/JBTIS-535 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.4.CR3 > Environment: Eclipse Luna for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > There is no category for installing SwitchYard tooling from Eclipse Marketplace -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3571) Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3571: ------------------------------------ Can we add the information here: https://access.stage.redhat.com/jbossnetwork/restricted/softwareDetail.ht... Or - must it be in a separate docuemnt/KBase article? > Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 > ------------------------------------------------------- > > Key: JBDS-3571 > URL: https://issues.jboss.org/browse/JBDS-3571 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Affects Versions: 9.0.0.CVE-2015-7501-GA > Reporter: Len DiMaggio > Assignee: Jiri Pallich > Fix For: 9.0.0.CVE-2015-7501-GA > > Attachments: patch.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-511) Add Fuse Data Trans to Eclipse Marketplace feature list

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-511?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-511. ----------------------------------- Verified with Eclipse Luna for JEE Developers and JBDS-IS 8.0.4 on marketplace > Add Fuse Data Trans to Eclipse Marketplace feature list > ------------------------------------------------------- > > Key: JBTIS-511 > URL: https://issues.jboss.org/browse/JBTIS-511 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Affects Versions: 8.0.4.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Labels: verified_jbdsis-8.0.4.CR3 > Fix For: 8.0.4.CR2 > > > Update devstudio EM feature list to include Fuse data transformation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015