[JBoss JIRA] (JBIDE-18262) exception on startup
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18262?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18262:
-------------------------------------
> What I do wonder though is why does all the examples have to know if they can be fixed at startup ?
This is something I can't speak to. [~fbricon] will need to comment.
> exception on startup
> --------------------
>
> Key: JBIDE-18262
> URL: https://issues.jboss.org/browse/JBIDE-18262
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> not sure what causes it but I'm getting this:
> java.lang.IllegalArgumentException: invalid version "6.0.0.CR01.1": invalid qualifier "CR01.1"
> at org.osgi.framework.Version.validate(Version.java:205)
> at org.osgi.framework.Version.<init>(Version.java:156)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher$RuntimeRangeRepresentation.matchesVersion(RuntimeMatcher.java:83)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:171)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:249)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130)
> at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:818)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18262) exception on startup
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18262?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18262:
-------------------------------------
When opening central, the examples are loaded it that background job. This loading is probably too much eager, we actually don't need to know if all the fixes are available at that time.
Looks like the 4th segment of the version crashes everything if it contains a dot. Maybe, for version comparison sakes, we could just replace this 4th segment dots with underscores
> exception on startup
> --------------------
>
> Key: JBIDE-18262
> URL: https://issues.jboss.org/browse/JBIDE-18262
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> not sure what causes it but I'm getting this:
> java.lang.IllegalArgumentException: invalid version "6.0.0.CR01.1": invalid qualifier "CR01.1"
> at org.osgi.framework.Version.validate(Version.java:205)
> at org.osgi.framework.Version.<init>(Version.java:156)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher$RuntimeRangeRepresentation.matchesVersion(RuntimeMatcher.java:83)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:171)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:249)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130)
> at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:818)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18252) "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18252?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18252:
-------------------------------------
The PR is safe, but it seems all it does is change the action to command handlers rather than the deprecated extension point used previously. I think it's safe, but in the end it seems a bit of an unnecessary patch. At this point though, it seems the new PR is the best idea.
> "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18252
> URL: https://issues.jboss.org/browse/JBIDE-18252
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Daniel Azarov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR1, 4.3.0.Alpha1
>
> Attachments: CannotPublishToServer.png
>
>
> There is a regression from JBIDE-15678 and JBIDE-18133
> Actions "Mark/Unmark as Deployable" do not working in Package Explorer with follow error:
> !CannotPublishToServer.png!
> Also these actions are not visible in editor context menu
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18238) Could not get monitored JVM error when Eclipse is started
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18238?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18238:
-------------------------------------
JVM monitor occasionally runs a jps command, which is a command to check java processes that are running. So odds are its the jps command itself. When you run jps, jps is run of the commands that is listed, since jps itself is also java.
> Could not get monitored JVM error when Eclipse is started
> ---------------------------------------------------------
>
> Key: JBIDE-18238
> URL: https://issues.jboss.org/browse/JBIDE-18238
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> When I start JBDS 8.0.0.CR1, I get this error in the error view:
> {code}
> Could not get monitored JVM.
> org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException:
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:248)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: java.lang.reflect.InvocationTargetException
> 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:483)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
> ... 5 more
> Caused by: sun.jvmstat.monitor.MonitorException: 14202 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> ... 10 more
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 13 more
> {code}
> This is in the workspace log:
> {code}
> !ENTRY org.jboss.tools.jmx.jvmmonitor.tools 4 0 2014-09-02 17:53:07.981
> !MESSAGE Could not get monitored JVM.
> !STACK 1
> org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException:
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:248)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: java.lang.reflect.InvocationTargetException
> 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:483)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
> ... 5 more
> Caused by: sun.jvmstat.monitor.MonitorException: 14202 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> ... 10 more
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 13 more
> !SUBENTRY 1 org.jboss.tools.jmx.jvmmonitor.core 4 0 2014-09-02 17:53:07.983
> !MESSAGE
> !STACK 0
> java.lang.reflect.InvocationTargetException
> 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:483)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: sun.jvmstat.monitor.MonitorException: 14202 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> ... 10 more
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 13 more
> Root exception:
> sun.jvmstat.monitor.MonitorException: 14202 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> 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:483)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.Tools.invokeGetMonitoredVm(Tools.java:246)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.addActiveJvm(JvmAttachHandler.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:106)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:73)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 13 more
> {code}
> One interesting thing is that it complains about "14202 not found", but the Eclipse process is actually 14197 and is shown in the JMX Navigator view. So I'm not sure where is other number comes from.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17616) Move 'externally managed' from launch config to server editor
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17616?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17616.
---------------------------------
Verified in JBDS 8.0.0.CR1 B201
> Move 'externally managed' from launch config to server editor
> -------------------------------------------------------------
>
> Key: JBIDE-17616
> URL: https://issues.jboss.org/browse/JBIDE-17616
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> in JBIDE-17076 externally managed was *moved* into launch UI even though that externally managed defaults to false and when users enable it launch configurations becomes irrelevant.
> Why can't we have it both so we do not have to get users to work with launch configuraiton UI for the simple case of not wanting to start a server but just connect to what is there ?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17924) java add annotation is available on projects but fail when running it
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17924?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-17924:
-----------------------------------
I don't see this. In my case the 'Finish' button is simply disabled...
> java add annotation is available on projects but fail when running it
> ---------------------------------------------------------------------
>
> Key: JBIDE-17924
> URL: https://issues.jboss.org/browse/JBIDE-17924
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Fix For: 4.2.0.CR1
>
>
> EXECUTE: Have an eclipse project in focus in explorer.
> EXECUTE: Cmd+4
>
> Java: Add Annotation shows up.
> Select it.
> result: error in log with this:
> org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.parser.java.facets.JavaSourceFacet] is installed.
> at org.jboss.forge.addon.facets.AbstractFaceted.getFacet(AbstractFaceted.java:51)
> at org.jboss.forge.addon.parser.java.beans.ProjectOperations.getProjectClasses(ProjectOperations.java:24)
> at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl.setupTargetClass(JavaAddAnnotationCommandImpl.java:296)
> at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl.initializeUI(JavaAddAnnotationCommandImpl.java:78)
> 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.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:65)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:81)
> at org.jboss.forge.addon.parser.java.ui.annotations.JavaAddAnnotationCommandImpl_$$_javassist_59bd122d-fa09-40ec-857b-60ae17012d9e.initializeUI(JavaAddAnnotationCommandImpl_$$_javassist_59bd122d-fa09-40ec-857b-60ae17012d9e.java)
> at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.initialize(SingleCommandControllerImpl.java:55)
> 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.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_3230b267-466d-40b8-9fd2-bd6828930098.initialize(CommandController_$$_javassist_3230b267-466d-40b8-9fd2-bd6828930098.java)
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.openWizard(WizardDialogHelper.java:103)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1$1.handleElementSelected(UICommandListDialog.java:187)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:326)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:316)
> at org.jboss.tools.forge.ui.internal.ext.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:347)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1504)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1632)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1500)
> at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1598)
> at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5719)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.superKeyDown(Widget.java:1908)
> at org.eclipse.swt.widgets.Widget.keyDown(Widget.java:1085)
> at org.eclipse.swt.widgets.Control.keyDown(Control.java:2400)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5629)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2329)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5691)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5128)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5277)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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)
> Caused by: org.jboss.forge.addon.facets.FacetNotFoundException: No Facet of type [interface org.jboss.forge.addon.parser.java.facets.JavaSourceFacet] is installed.
> ... 76 more
> I would have expected either:
> a) not having add annotation on projects
> b) when running forge would report a more informative error on why it is failing
> c) run add annotation but let me select which file it is for...
> anything except this silent logged error ;)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17936.
---------------------------------
Verified in JBDS 8.0.0.CR1 B201
> Remote deploy only server has wrong temp dir and unreadable entries in server editor
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17936
> URL: https://issues.jboss.org/browse/JBIDE-17936
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3b B193
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
> Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png
>
>
> This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one:
> When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems:
> 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big.
> !deploy-only-crop.png!
> See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before.
> 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18179) Forge Console is limited to 80 chars and throws exception if line surpasses the limit
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18179?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-18179.
-------------------------------
Resolution: Done
> Forge Console is limited to 80 chars and throws exception if line surpasses the limit
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18179
> URL: https://issues.jboss.org/browse/JBIDE-18179
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> {code}
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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:483)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18179) Forge Console is limited to 80 chars and throws exception if line surpasses the limit
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18179?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-18179:
-----------------------------------
Great work George! Thx!
> Forge Console is limited to 80 chars and throws exception if line surpasses the limit
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18179
> URL: https://issues.jboss.org/browse/JBIDE-18179
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> {code}
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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:483)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months