[JBoss JIRA] (JBIDE-22290) Open via livereload quick access errors when no livereload server is present
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22290?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22290:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Open via livereload quick access errors when no livereload server is present
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22290
> URL: https://issues.jboss.org/browse/JBIDE-22290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.6.x
>
>
> The following error is produced while the livereload server is starting:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4522)
> at org.eclipse.swt.SWT.error(SWT.java:4437)
> at org.eclipse.swt.SWT.error(SWT.java:4408)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:189)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:114)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:112)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$2.done(LaunchLiveReloadServerCommandHandler.java:67)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22949) IllegalArgumentException below PreferencesUtil.getAbsolutePathToConfigurationFolder (thrown in File.<init>)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22949?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22949:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> IllegalArgumentException below PreferencesUtil.getAbsolutePathToConfigurationFolder (thrown in File.<init>)
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22949
> URL: https://issues.jboss.org/browse/JBIDE-22949
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Plug-in org.jboss.tools.browsersim.eclipse was unable to load class org.jboss.tools.browsersim.eclipse.console.ConsolePageParticipant.
> {noformat}
> java.lang.IllegalArgumentException: URI has an authority component
> at java.io.File.<init>(null:-1)
> at org.jboss.tools.browsersim.eclipse.preferences.PreferencesUtil.getAbsolutePathToConfigurationFolder(PreferencesUtil.java:200)
> at org.jboss.tools.browsersim.eclipse.Activator.backportPreferences(Activator.java:96)
> at org.jboss.tools.browsersim.eclipse.Activator.start(Activator.java:86)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(null:-2)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:334)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(null:-1)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.ui.internal.console.ConsolePageParticipantExtension.createDelegate(ConsolePageParticipantExtension.java:72)
> at org.eclipse.ui.internal.console.ConsoleManager.getPageParticipants(ConsoleManager.java:455)
> at org.eclipse.ui.internal.console.ConsoleView.doCreatePage(ConsoleView.java:315)
> at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:400)
> at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:743)
> at org.eclipse.ui.internal.console.ConsoleView$4.run(ConsoleView.java:395)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
> {noformat}
> Bundles:
> | org.eclipse.osgi | 3.11.0.v20160603-1336 | 3.11.0.v20160603-1336 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.console | 3.6.200.v20160518-1858 | 3.6.200.v20160518-1858 |
> | org.jboss.tools.browsersim.eclipse | 3.8.0.Final-v20160609-2253-B3 | 3.8.0.Final-v20160609-2253-B3 |
> Operating Systems:
> | Windows | 6.3.0 | 6.3.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/579a0fafe4b0fe642b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-24579) Can't import push-helloworld-cordova project
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24579?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24579:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Can't import push-helloworld-cordova project
> --------------------------------------------
>
> Key: JBIDE-24579
> URL: https://issues.jboss.org/browse/JBIDE-24579
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.5.0.AM1
> Environment: JBT 4.5.0.AM1 (stage) or devstudio-11.0.0.AM1-v20170622-1352-B295, Fedora 25 (wayland disabled), openjdk version "1.8.0_131"
> Reporter: Lukáš Valach
> Assignee: Fred Bricon
> Fix For: 4.6.x
>
> Attachments: push-helloworld-cordova.png
>
>
> I can't install "push-helloworld-cordova" project from RH Central. During the installation I got a window with message *"push-helloworld-cordova project has not been fully imported. Check if it is defined correctly"*. I see that the project has been downloaded successfully but it wasn't imported (it isn't displayed in Project Explorer).
> I tried to import project from the disk into the Eclipse and it worked without problems. There is no error in the log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22939) 3rd party caused XPCOMException below VpeAbstractBodyTemplate.create
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22939?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22939:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> 3rd party caused XPCOMException below VpeAbstractBodyTemplate.create
> --------------------------------------------------------------------
>
> Key: JBIDE-22939
> URL: https://issues.jboss.org/browse/JBIDE-22939
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: The function "setAttribute" returned an error condition (0x80530005)
> {noformat}
> org.mozilla.xpcom.XPCOMException: The function "setAttribute" returned an error condition (0x80530005)
> at EXTERNAL.EXTERNAL(null:-1)
> at com.sun.proxy.$Proxy.setAttribute(null:-1)
> at org.jboss.tools.vpe.editor.template.VpeAbstractBodyTemplate.create(VpeAbstractBodyTemplate.java:76)
> at org.jboss.tools.vpe.editor.template.VpeTemplateSafeWrapper.create(VpeTemplateSafeWrapper.java:73)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:372)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:476)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateElement(VpeVisualDomBuilder.java:809)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:765)
> at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:735)
> at org.jboss.tools.vpe.editor.VpeController$VPEUpdateJob.runInUIThread(VpeController.java:1284)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.7.1.Final-v20160331-0327-B91 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5756bb0be4b06056d2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19342:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Update code to cope with generics added to org.eclipse.core.runtime package API
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19342
> URL: https://issues.jboss.org/browse/JBIDE-19342
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common, cordovasim, forge, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html-source-editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.6.x
>
>
> We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API.
> From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html :
> {quote}
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021
> Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25
> Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common:
> 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)"
> 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented.
> 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All)
> 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature.
> Typical change:
> Old:
> {code}
> public Object getAdapter(Class adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return getCompilationUnit();
> return null;
> }
> {code}
> New:
> {code}
> public <T> T getAdapter(Class<T> adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return adapter.cast(getCompilationUnit());
> return null;
> }
> {code}
> 5. Update implementations of IAdapterFactory
> Hint for 4. & 5.:
> - Open Type Hierarchy on IAdaptable, etc.
> - In the view menu, select a working set that contains your projects
> - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22346) NullPointerException in JaxrsResourceMethodValidatorDelegate.resolveAnnotationParamSourceRange
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22346?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22346:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NullPointerException in JaxrsResourceMethodValidatorDelegate.resolveAnnotationParamSourceRange
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22346
> URL: https://issues.jboss.org/browse/JBIDE-22346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message:
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.resolveAnnotationParamSourceRange(JaxrsResourceMethodValidatorDelegate.java:445)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validateNoUnboundPathAnnotationTemplateParameters(JaxrsResourceMethodValidatorDelegate.java:291)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:87)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:69)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceValidatorDelegate.internalValidate(JaxrsResourceValidatorDelegate.java:67)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceValidatorDelegate.internalValidate(JaxrsResourceValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:69)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:490)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:422)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> {noformat}
> Bundles:
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57265dcae4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months