[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3924:
-----------------------------
Fix Version/s: 12.x
(was: 10.x)
> Installation looks incomplete but is actually completed
> -------------------------------------------------------
>
> Key: JBDS-3924
> URL: https://issues.jboss.org/browse/JBDS-3924
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.GA
> Environment: Fedora 22 (fixed, not 23)
> Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
> jvm: java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Labels: install, installation, installer
> Fix For: 12.x
>
> Attachments: devstudio10install.png, incomplete_install.png
>
>
> Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3908) NPE creating Top down jax-ws service
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3908?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3908:
-----------------------------
Fix Version/s: 12.x
(was: 10.x)
> NPE creating Top down jax-ws service
> ------------------------------------
>
> Key: JBDS-3908
> URL: https://issues.jboss.org/browse/JBDS-3908
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 10.0.0.Alpha2
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
> Fix For: 12.x
>
>
> I get this error when trying to create a service from wsdl:
> {noformat}IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:120)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:437)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:353)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:993)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:869)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> 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.GeneratedMethodAccessor131.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> 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:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492){noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3907) NPE when invoking service from web service tester
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3907?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3907:
-----------------------------
Fix Version/s: 12.x
(was: 10.x)
> NPE when invoking service from web service tester
> -------------------------------------------------
>
> Key: JBDS-3907
> URL: https://issues.jboss.org/browse/JBDS-3907
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 10.0.0.Alpha2
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 12.x
>
>
> I have a project with a jax-ws service deployed on wildfly. Select the service wsdl -> test in jboss web service tester. Clicking invoke shows this error:
> {noformat}
> An internal error occurred during: "Invoking web service...".
> java.lang.NullPointerException
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1909)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3730:
-----------------------------
Fix Version/s: 12.x
(was: 11.x)
> Headless standalone installer can be run with xml config that contains eap bundle
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3730
> URL: https://issues.jboss.org/browse/JBDS-3730
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 12.x
>
>
> One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following:
> {noformat}[ Starting automated installation ]
> [INFO] Selected JVM Information
> [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64
> [INFO] Vendor : Oracle Corporation
> [INFO] Version : 1.8.0_72
> [INFO] Arch : 64-bit
> [ Starting to unpack ]
> [ Processing package: P2 Director Application (1/4) ]
> [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ]
> [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ]
> [ Processing package: JBoss Enterprise Application Platform (4/4) ]
> [ WARNING: Error executing
> /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ]
> [ ERROR: The installation was not completed ]
> [ Unpacking finished ]
> com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19)
> com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19)
> at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source)
> at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
> at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
> at com.izforge.izpack.installer.Installer.main(Unknown Source)
> [ Automated installation FAILED! ]{noformat}
> The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3727:
-----------------------------
Fix Version/s: 12.x
(was: 11.x)
> Installer fails with not normalized paths
> -----------------------------------------
>
> Key: JBDS-3727
> URL: https://issues.jboss.org/browse/JBDS-3727
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 12.x
>
>
> The installer accepts installation paths with the following format:
> {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat}
> With such a path it fails immediately after the installation starts with the following exception:
> {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448)
> at java.lang.Thread.run(Thread.java:745){noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3645) Installation of JBoss Developer Studio to a network drive fails
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3645?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3645:
-----------------------------
Fix Version/s: 12.x
(was: 11.x)
> Installation of JBoss Developer Studio to a network drive fails
> ----------------------------------------------------------------
>
> Key: JBDS-3645
> URL: https://issues.jboss.org/browse/JBDS-3645
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.1.0.GA
> Environment: * Windows Server 2012
> Reporter: Takayuki Konishi
> Assignee: Denis Golovin
> Fix For: 12.x
>
>
> A customer is trying to install 64 bit jboss developer studio 8.1 using java 1.8 64 bit on a network drive (32 bit) from their local 64 bit machine.
> Installation failed with the error, see the attached error message:
> {code}
> !SESSION 2016-02-16 16:05:32.385 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_65
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -roaming -r jar:file:///E:/downloads/jboss-devstudio-8.1.0.GA-installer-standalone.jar!/ -d E:\tools\eclipse\studio -p jbds -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.jsdt.feature.patch.feature.group -profileProperties org.eclipse.update.install.features=true
> Command-line arguments: -roaming -r jar:file:///E:/downloads/jboss-devstudio-8.1.0.GA-installer-standalone.jar!/ -d E:\tools\eclipse\studio -p jbds -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.jsdt.feature.patch.feature.group -profileProperties org.eclipse.update.install.features=true
> !ENTRY org.eclipse.equinox.p2.engine 4 4 2016-02-16 16:27:12.468
> !MESSAGE An error occurred while installing the items
> !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2016-02-16 16:27:12.468
> !MESSAGE session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.rse.subsystems.shells.telnet 1.2.300.201403100950, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2016-02-16 16:27:12.468
> !MESSAGE The artifact file for osgi.bundle,org.eclipse.rse.subsystems.shells.telnet,1.2.300.201403100950 was not found.
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4321:
-----------------------------
Fix Version/s: 12.x
(was: 11.x)
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Jeff MAURY
> Fix For: 12.x
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_Fedora24_strict.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_RHEL7_strict.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months