[JBoss JIRA] (JBIDE-19748) No error or message is displayed when a project namespace has no templates
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19748?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19748:
----------------------------------
Fix Version/s: 4.3.0.Beta1
> No error or message is displayed when a project namespace has no templates
> --------------------------------------------------------------------------
>
> Key: JBIDE-19748
> URL: https://issues.jboss.org/browse/JBIDE-19748
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> The following error when no templates are in a project namespace:
> 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.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:583)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1001)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:700)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1349)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:353)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:906)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:617)
> at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:815)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541)
> at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790)
> at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423)
> at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701)
> at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.createTemplatesViewer(ResourcesDetailsPage.java:66)
> at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.doCreateControls(ResourcesDetailsPage.java:48)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.createWizardDialog(WizardUtils.java:53)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:74)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:67)
> at org.jboss.tools.openshift.internal.ui.command.NewApplicationHandler.execute(NewApplicationHandler.java:36)
> 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: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)
> ... 38 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19748) No error or message is displayed when a project namespace has no templates
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19748?page=com.atlassian.jira.plugi... ]
Jeff Cantrill closed JBIDE-19748.
---------------------------------
Resolution: Done
> No error or message is displayed when a project namespace has no templates
> --------------------------------------------------------------------------
>
> Key: JBIDE-19748
> URL: https://issues.jboss.org/browse/JBIDE-19748
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> The following error when no templates are in a project namespace:
> 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.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:583)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1001)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:700)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1349)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:353)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:906)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:617)
> at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:815)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541)
> at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790)
> at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423)
> at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701)
> at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.createTemplatesViewer(ResourcesDetailsPage.java:66)
> at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.doCreateControls(ResourcesDetailsPage.java:48)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.createWizardDialog(WizardUtils.java:53)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:74)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:67)
> at org.jboss.tools.openshift.internal.ui.command.NewApplicationHandler.execute(NewApplicationHandler.java:36)
> 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: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)
> ... 38 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-423:
-------------------------------------------
thanks and about category not needed to be delcared that makes sense since the "EA" catalog is more an overlay than an independent discovery set.
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
> ---------------------------------------------------------------------------------
>
> Key: JBTIS-423
> URL: https://issues.jboss.org/browse/JBTIS-423
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.GA
> Environment: JBDS 8.1.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 8.0.2.GA
>
> Attachments: ea1.png
>
>
> When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log
> {code}
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources:
> com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar,
> com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19755:
---------------------------------------------
management and tcp/ip monitor only uses http afaik ...so why is this not okey ? (i agree the upstream should be fixed since seems like a weird limitation)
> Implement ServerPort portion of wst.servertools API
> ---------------------------------------------------
>
> Key: JBIDE-19755
> URL: https://issues.jboss.org/browse/JBIDE-19755
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, upstream
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it.
> Unfortunately, I've been hit by an upstream bug that hinders my progress:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109
> To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19637:
---------------------------------------
Doesn't work for me :( I pull this PR, built using "mvn clean verify -DskipTests -DskipITests", then installed on top of jbt nightly from yesterday (actually it did an update), then restarted Eclipse. Still the same problem. Then I tried a new workspace, still no luck.
> Runtime download not working from New Server dialog
> ---------------------------------------------------
>
> Key: JBIDE-19637
> URL: https://issues.jboss.org/browse/JBIDE-19637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: help_wanted
> Fix For: 4.3.0.Beta1
>
>
> When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything.
> If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work.
> This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19697:
---------------------------------------
OK, thanks for the link, [~maxandersen] :) That explains where those two entries at the top of the list (screenshot above) are coming from. Again, as I said, they are ignored by default - exactly as expected.
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta1
>
> Attachments: pref-recorder.png, preference-recorder.png
>
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19638) Web Service wizard - drop-down menus too narrow by default
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19638?page=com.atlassian.jira.plugi... ]
Jan Richter commented on JBIDE-19638:
-------------------------------------
My Fedora is using GTK 3.10.9
> Web Service wizard - drop-down menus too narrow by default
> ----------------------------------------------------------
>
> Key: JBIDE-19638
> URL: https://issues.jboss.org/browse/JBIDE-19638
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
> Attachments: bundles.info, ws.png, wstester.png
>
>
> By default the drop down menus for 'web service type' and 'client type' are too narrow (vertically) for the text inside them to be rendered properly.
> Resizing the wizard in any way will resize the drop downs to standard height which won't change from that moment on.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months