[JBoss JIRA] (JBIDE-24116) NullPointerException in JSFPromptingProvider.getVariables
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24116?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24116:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NullPointerException in JSFPromptingProvider.getVariables
> ---------------------------------------------------------
>
> Key: JBIDE-24116
> URL: https://issues.jboss.org/browse/JBIDE-24116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Reporter: Automated Error Reporting Bot
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message:
> java.lang.NullPointerException: null
> at org.jboss.tools.jsf.model.pv.JSFPromptingProvider.getVariables(JSFPromptingProvider.java:268)
> at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:144)
> at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:103)
> at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:83)
> at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:466)
> at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:282)
> at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolve(AbstractELCompletionEngine.java:165)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337)
> at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validate(ELValidator.java:278)
> 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.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259)
> at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95)
> at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269)
> at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321)
> at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691)
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.2.v20161113-1700 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.eclipse.wst.xml.ui | 1.1.501.v201501212057 | 1.1.700.v201604272318 |
> | org.jboss.tools.common.el.core | 3.7.1.Final-v20160408-2358-B112 | 3.8.3.v20161213-1258 |
> | org.jboss.tools.common.text.xml | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160607-2053 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.3.v20161213-1258 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.3.v20161214-1452 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.3.v20161214-1634 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160628-0959 |
> Operating Systems:
> | Linux | 4.7.10.fc23 | 4.8.8.fc24 |
> | MacOSX | 10.11.6 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/574e5d77e4b06056d20... 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-19790) Limit the possible Hibernate runtime choices to only the supported ones in the JPA generation dialogs
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19790?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19790:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Limit the possible Hibernate runtime choices to only the supported ones in the JPA generation dialogs
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19790
> URL: https://issues.jboss.org/browse/JBIDE-19790
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.3.0.Alpha2
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.3.x, 4.6.x
>
>
> - Create a maven project
> - Add hibernate-entitymanager dependencies (I used version 4.3.9.Final)
> - Convert into JPA project: choose JPA 2.1 with the Hibernate platform
> - JPA Tools -> Generate Entities from Tables
> -- Do not use Console Configuration
> -- Choose anything else than 4.3 for the Hibernate version
> => The dialog will fail because no console configuration can be created for the chosen Hibernate version
> - The same problem is present when generating the DDL from the entities and disabling the console configuration use
> - The dropdown in the generation dialog should only offer Hibernate versions that are compatible with the chosen JPA version
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22353) TimeoutException in JettyServerRunner.start
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22353?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22353:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> TimeoutException in JettyServerRunner.start
> -------------------------------------------
>
> Key: JBIDE-22353
> URL: https://issues.jboss.org/browse/JBIDE-22353
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> 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: Failed to create or start LiveReload proxy for server wildfly at OpenShift 3 (10.1.2.2)
> {noformat}
> java.util.concurrent.TimeoutException: Failed to start Proxy Server (50347 -> 80) within expected time (reason: timeout)
> at org.jboss.tools.livereload.core.internal.server.jetty.JettyServerRunner.start(JettyServerRunner.java:72)
> at org.jboss.tools.livereload.core.internal.server.wst.LiveReloadServerBehaviour.startProxy(LiveReloadServerBehaviour.java:344)
> at org.jboss.tools.livereload.core.internal.server.wst.LiveReloadServerBehaviour.inform(LiveReloadServerBehaviour.java:304)
> at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:58)
> at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.serverChanged(ServerLifeCycleListener.java:120)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:745)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:653)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
> at org.jboss.tools.openshift.core.server.OpenShiftServerBehaviour.setServerStarted(OpenShiftServerBehaviour.java:38)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.checkServerState(OpenShiftLaunchController.java:143)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:113)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160209-0147 | 3.8.0.v20160209-0147 |
> | org.eclipse.debug.core | 3.10.100.v20160203-1134 | 3.10.100.v20160203-1134 |
> | org.eclipse.wst.server.core | 1.8.100.v201603031514 | 1.8.100.v201603031514 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.0.Alpha1-v20160505-0626-B966 | 3.2.0.Alpha1-v20160505-0626-B966 |
> | org.jboss.tools.livereload.core | 1.4.0.Alpha1-v20160401-2041-B449 | 1.4.0.Alpha1-v20160401-2041-B449 |
> | org.jboss.tools.openshift.core | 3.2.0.qualifier | 3.2.0.qualifier |
> Operating Systems:
> | MacOSX | 10.10.5 | 10.10.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572cf573e4b0a54983...] 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-22342) NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in WebAnnotationReader.analyzeCompilationUnit)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22342?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22342:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in WebAnnotationReader.analyzeCompilationUnit)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22342
> URL: https://issues.jboss.org/browse/JBIDE-22342
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jdt.core".
> {noformat}
> java.lang.NullPointerException: null
> at org.eclipse.jst.jee.model.internal.WebAnnotationReader.analyzeCompilationUnit(WebAnnotationReader.java:144)
> at org.eclipse.jst.jee.model.internal.WebAnnotationReader.processAddedCompilationUnit(WebAnnotationReader.java:257)
> at org.eclipse.jst.jee.model.internal.WebAnnotationReader.processChangedCompilationUnit(WebAnnotationReader.java:270)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.recursevilyProcessCompilationUnits(AbstractAnnotationModelProvider.java:553)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.internalPostReconcile(AbstractAnnotationModelProvider.java:466)
> at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.elementChanged(AbstractAnnotationModelProvider.java:446)
> at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1662)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1652)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1504)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1463)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1250)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1227)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1192)
> at org.jboss.tools.websockets.ui.internal.ca.SocketProposalComputer.computeCompletionProposals(SocketProposalComputer.java:130)
> at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:333)
> at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:337)
> at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:322)
> at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:279)
> at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499)
> at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:384)
> 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.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 |
> | org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.jboss.tools.websockets.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572b697de4b0a54983...] 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-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21877:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: connection_wizard, openshift_v3
> Fix For: 4.6.x
>
> Attachments: screenshot-1.png
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23402:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> [WATCHER] Explorer: can "Deploy Latest" even if the build failed
> ----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Fix For: 4.6.x
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22812) NullPointerException in CommandUtil.toUrl
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22812?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22812:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NullPointerException in CommandUtil.toUrl
> -----------------------------------------
>
> Key: JBIDE-22812
> URL: https://issues.jboss.org/browse/JBIDE-22812
> 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: Unhandled event loop exception
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.browsersim.eclipse.util.CommandUtil.toUrl(CommandUtil.java:222)
> at org.jboss.tools.browsersim.eclipse.util.CommandUtil.getUrlFromSelection(CommandUtil.java:194)
> at org.jboss.tools.browsersim.eclipse.util.CommandUtil.guessUrl(CommandUtil.java:77)
> at org.jboss.tools.browsersim.eclipse.handlers.RunBrowserSimHandler.execute(RunBrowserSimHandler.java:28)
> 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(NativeMethodAccessorImpl.java:-2)
> 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:56)
> {noformat}
> Bundles:
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.browsersim.eclipse | 3.7.1.Final-v20160331-0511-B89 | 3.7.1.Final-v20160331-0511-B89 |
> 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/573739a1e4b0138d62...] 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