[JBoss JIRA] (JBDS-3067) Use JBDevStudio.icns with higher resolution on mac
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3067?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3067:
-------------------------------------
I released new generated icns file with amx resolution 256x256 and original png files into master and jbosstools-4.2.x branch, we have to take care about three more resolutions, but it can wait.
> Use JBDevStudio.icns with higher resolution on mac
> --------------------------------------------------
>
> Key: JBDS-3067
> URL: https://issues.jboss.org/browse/JBDS-3067
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Environment: Mac OS X 10.9.3 (Mavericks)
> Reporter: Denis Golovin
> Assignee: Daniel Azarov
> Priority: Minor
> Labels: respin-a
> Fix For: 9.0.0.Alpha1
>
> Attachments: jbds-in-finder.png
>
>
> Current icon resolution is too low and looks like this
> !jbds-in-finder.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17598) Arquillian run launcher crash
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17598?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-17598.
-----------------------------------
Resolution: Duplicate Issue
A duplicate of JBIDE-17595.
> Arquillian run launcher crash
> -----------------------------
>
> Key: JBIDE-17598
> URL: https://issues.jboss.org/browse/JBIDE-17598
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta3
>
>
> The launcher dialog crashes (disappears) when I try to run test on project with non-standard maven dierctory structure with the following error:
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?))
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1666)
> at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:640)
> at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab$1$1.run(ArquillianTab.java:151)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> ... 24 more
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17598) Arquillian run launcher crash
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17598?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17598:
----------------------------------
Fix Version/s: 4.2.0.Beta3
(was: 4.2.0.CR2)
> Arquillian run launcher crash
> -----------------------------
>
> Key: JBIDE-17598
> URL: https://issues.jboss.org/browse/JBIDE-17598
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta3
>
>
> The launcher dialog crashes (disappears) when I try to run test on project with non-standard maven dierctory structure with the following error:
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?))
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1666)
> at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:640)
> at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab$1$1.run(ArquillianTab.java:151)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> ... 24 more
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-289?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-289:
-----------------------------------------
Yes, that would be great [~pleacu]. Looks like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-esb-4.1.x/1253/ is the last blue build that's up on Jenkins.
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
> ----------------------------------------------------------------
>
> Key: JBTIS-289
> URL: https://issues.jboss.org/browse/JBTIS-289
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: ESB
> Affects Versions: 4.0.0
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.0
>
>
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> Steps as defined by Nick (thanks Nick!):
> a) the contents of the examples are in a former employee's SVN workspace
> and haven't been updated since a couple of years. They don't really work
> as well as they could.
> b) the examples are all mostly duplicated in the quickstarts folder that
> ships with SOA-P 5.3.1. See
> https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
> https://issues.jboss.org/browse/JBTIS-62
> Basically, we need to:
> * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
> eclipse projects (merge in contents from duplicate examples in Denny's
> workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
> if not, no great need.
> * copy the older examples that are not already in SOA-P 5.3 - the ones
> that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
> available there.
> * update the BPEL Examples guide as needed
> * document the fact that these examples are no longer available as
> importable zipped example projects contributed by a plugin, but rather
> as already-unpacked projects nested within the SOA-P runtime zip
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-293.
------------------------------
Fix Version/s: 4.2.0.Alpha2
8.0.0.Alpha2
Resolution: Done
Corrected by Lars with his refactoring in the latest Fuse tooling.
> Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTIS-293
> URL: https://issues.jboss.org/browse/JBTIS-293
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.2.0.Alpha2, 8.0.0.Alpha2
>
>
> If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don't get this error.
> SESSION 2014-07-30 09:22:59.386 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_60-ea
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975]
> Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model
> -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"
> org.fusesource.ide.camel.model [977]
> No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> require: (osgi.wiring.bundle=org.eclipse.core.runtime)
> |
> provide: osgi.wiring.bundle: org.eclipse.core.runtime
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"]
> Chain 2:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> import: (osgi.wiring.package=org.fusesource.camel.tooling.util)
> |
> export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model
> io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"]
> import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0))))
> |
> export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters
> org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"]
> import: (osgi.wiring.package=javax.xml.bind.annotation.adapters)
> |
> export: osgi.wiring.package: javax.xml.bind.annotation.adapters
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-289) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-289?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-289:
----------------------------------
Hey [~bfitzpat] - I'm assembling a kepler maintenance release of the IS now (JBTIS 4.1.6/ JBDSIS 7.0.3) - should we build/promote a kepler version of ESB with your examples fix?
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration - 4.1.x
> ----------------------------------------------------------------
>
> Key: JBTIS-289
> URL: https://issues.jboss.org/browse/JBTIS-289
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: ESB
> Affects Versions: 4.0.0
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.0
>
>
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> Steps as defined by Nick (thanks Nick!):
> a) the contents of the examples are in a former employee's SVN workspace
> and haven't been updated since a couple of years. They don't really work
> as well as they could.
> b) the examples are all mostly duplicated in the quickstarts folder that
> ships with SOA-P 5.3.1. See
> https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
> https://issues.jboss.org/browse/JBTIS-62
> Basically, we need to:
> * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
> eclipse projects (merge in contents from duplicate examples in Denny's
> workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
> if not, no great need.
> * copy the older examples that are not already in SOA-P 5.3 - the ones
> that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
> available there.
> * update the BPEL Examples guide as needed
> * document the fact that these examples are no longer available as
> importable zipped example projects contributed by a plugin, but rather
> as already-unpacked projects nested within the SOA-P runtime zip
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15517) Explorer: There's currently no way to see that an application is scaled
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15517?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-15517:
---------------------------------------
[~adietish] Is it correct this feature is to make it possible for someone to determine if it 'CAN' scale instead of 'is scaled'. We have no synced state to know an application is actually scaled right?
> Explorer: There's currently no way to see that an application is scaled
> -----------------------------------------------------------------------
>
> Key: JBIDE-15517
> URL: https://issues.jboss.org/browse/JBIDE-15517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Labels: explorer
> Fix For: 4.3.x
>
>
> There's currently no way for the user to see that an application is scaled.
> We should show this to the user via decorations in the OpenShift Explorer and also in the application details.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-15517) Explorer: There's currently no way to see that an application is scaled
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15517?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-15517:
----------------------------------
Summary: Explorer: There's currently no way to see that an application is scaled (was: Explorer: There's currently no way to see that an appliaction is scaled)
> Explorer: There's currently no way to see that an application is scaled
> -----------------------------------------------------------------------
>
> Key: JBIDE-15517
> URL: https://issues.jboss.org/browse/JBIDE-15517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Labels: explorer
> Fix For: 4.3.x
>
>
> There's currently no way for the user to see that an application is scaled.
> We should show this to the user via decorations in the OpenShift Explorer and also in the application details.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months