[JBoss JIRA] (JBIDE-22301) NPE in new OS application from eclipse project with no remote git reference.
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-22301 at 6/2/16 12:34 PM:
------------------------------------------------------------------------
[~mlabuda], the only relevant change is fix JBIDE-22420 applied on May, 25, but it could not fix what I found in PR 1205. Could you please compare the two builds doing the same steps in the wizard?
was (Author: scabanovich):
[~mlabuda], the only relevant change is fix JBIDE-22420 applied on May, 25, but it could not what I found in PR 1205. Could you please compare the two builds doing the same steps in the wizard?
> NPE in new OS application from eclipse project with no remote git reference.
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22301
> URL: https://issues.jboss.org/browse/JBIDE-22301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha2
>
>
> Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE:
> {noformat:title=Unhandled event loop exception}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> 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:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> 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.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.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:491)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> 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:150)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3914:
-----------------------------
Target Release: (was: )
> Build zip distribution for Mac OS X and Linux
> ---------------------------------------------
>
> Key: JBDS-3914
> URL: https://issues.jboss.org/browse/JBDS-3914
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Denis Golovin
> Fix For: 10.0.0.GA
>
> Attachments: zip in exe fails.png
>
>
> We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3914:
-----------------------------
Attachment: zip in exe fails.png
Trivial solution: embed a zip instead of a .7z in the sfx exe: https://github.com/redhat-developer-tooling/developer-platform-install/pu...
Build looks fine, zip can be unpacked on linux and the contained jbds.jar launches fine.
HOWEVER, the .exe on windows now does this:
!zip in exe fails.png!
> Build zip distribution for Mac OS X and Linux
> ---------------------------------------------
>
> Key: JBDS-3914
> URL: https://issues.jboss.org/browse/JBDS-3914
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Denis Golovin
> Fix For: 10.0.0.GA
>
> Attachments: zip in exe fails.png
>
>
> We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22481) For JBIDE 4.4.0.Final: Prepare for Final/GA [Integration Tests]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22481?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22481:
----------------------------------------
I've created the branch.
> For JBIDE 4.4.0.Final: Prepare for Final/GA [Integration Tests]
> ---------------------------------------------------------------
>
> Key: JBIDE-22481
> URL: https://issues.jboss.org/browse/JBIDE-22481
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Final
>
>
> For JBIDE 4.4.0.Final [Integration Tests]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch
> 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.x
> git push origin jbosstools-4.4.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!)
> * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
> 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22481) For JBIDE 4.4.0.Final: Prepare for Final/GA [Integration Tests]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22481?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-22481.
----------------------------------
Resolution: Done
> For JBIDE 4.4.0.Final: Prepare for Final/GA [Integration Tests]
> ---------------------------------------------------------------
>
> Key: JBIDE-22481
> URL: https://issues.jboss.org/browse/JBIDE-22481
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Final
>
>
> For JBIDE 4.4.0.Final [Integration Tests]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch
> 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.x
> git push origin jbosstools-4.4.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!)
> * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
> 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3918) Latest DevStudio build starts without splash screen
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3918?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3918:
-----------------------------
Attachment: jbds10-splash-win10-fixed.png
Fixed in build 5501:
!jbds10-splash-win10-fixed.png!
> Latest DevStudio build starts without splash screen
> ---------------------------------------------------
>
> Key: JBDS-3918
> URL: https://issues.jboss.org/browse/JBDS-3918
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: p2-product
> Affects Versions: 10.0.0.GA
> Environment: OS:
> Windows 10
> Devstudio:
> Version: 10.0.0.Alpha3
> Build id: Alpha3-v20160601-0425-B5485
> Build date: 20160601-0425
> Reporter: Denis Golovin
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.0.0.GA
>
> Attachments: jbds10-splash-win10-fixed.png
>
>
> Latest nightly build downloaded bu Development Suite installer starts without splash screen
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22501:
---------------------------------------
I did see it before, but that was before JBDS-3739 was fixed, so the whole experience was broken anyway. But you're correct, it's not 100 % reproducible unfortunately. I will ask some other colleagues to try as well.
> CDK stuck on Starting... after launch
> -------------------------------------
>
> Key: JBIDE-22501
> URL: https://issues.jboss.org/browse/JBIDE-22501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.x
>
>
> This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this.
> This is what I did today (verifying JBDS-3739):
> 1. Start my Eclipse Neon RC2
> 2. Updated Eclipse
> 3. Updated Docker Tools to latest nightly
> 4. Installed nightly JBoss Tools Abridged
> 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before)
> 6. Start CDK server
> Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked.
> 7. Stop CDK server
> 8. Start CDK server
> This time it's stuck on Starting... even though I can see from the console that the vagrant box started:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Remote connection disconnect. Retrying...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always will still run.
> {code}
> Now it will probably time out and stop the server. And most probably next start will work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months