[JBoss JIRA] (JBIDE-19693) Exception when invoking code assist for external HTML file
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19693?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-19693.
-------------------------------
Verified with JBT 4.3.0-Beta1-v20150528-2309-B9993
> Exception when invoking code assist for external HTML file
> ----------------------------------------------------------
>
> Key: JBIDE-19693
> URL: https://issues.jboss.org/browse/JBIDE-19693
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64 bit, Oracle JDK 1.7
> Reporter: Vlado Pakan
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> 1. Open external html file in VPE
> 2. Invoke code assist
> ERROR (appears 3 times):
> {noformat}
> !ENTRY org.jboss.tools.jst.web.ui 4 0 2015-04-23 08:57:43.421
> !MESSAGE Cannot find existing file by its document.
> !STACK 0
> java.lang.IllegalStateException: Cannot find existing file by its document.
> at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.AbstractXmlCompletionProposalComputer.createContext(AbstractXmlCompletionProposalComputer.java:125)
> at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.FaceletsELCompletionProposalComputer.createContext(FaceletsELCompletionProposalComputer.java:127)
> at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:83)
> at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.FaceletsELCompletionProposalComputer.computeCompletionProposals(FaceletsELCompletionProposalComputer.java:74)
> at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284)
> at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:290)
> at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:484)
> at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:255)
> at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127)
> 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:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3790)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19695) Annoying message "Be sure, may be you also should rename setter methods to avoid compilation problems."
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19695?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-19695.
-------------------------------
Verified with JBT 4.3.0-Beta1-v20150528-2309-B9993
> Annoying message "Be sure, may be you also should rename setter methods to avoid compilation problems."
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19695
> URL: https://issues.jboss.org/browse/JBIDE-19695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, jsp/jsf/xml/html source editing, seam2
> Affects Versions: 4.2.3.Final
> Reporter: Clovis Seragiotto
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta1
>
> Attachments: after installation.png, renaming a get method.png, Version chosen.png
>
>
> When renaming a get-method in Eclipse, the warning "Be sure, may be you also should rename setter methods to avoid compilation problems." is displayed.
> It should be possible to turn this warning off (and the sentence should be fixed).
> By Googling the message, I found:
> JBoss Tools SVN: r40216 - trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/core.
> That is why I suppose the right component is seam.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19845) Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19845?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19845:
-------------------------------------
Comment: was deleted
(was: IMHO we're starting from context menu with a connection (or a domain) selected (otherwise "New->Application" wouldnt show up). Thus it's clear for what connection the user wants to create an application. I tested in JBDS8 and that's how it behaved, you couldnt choose a different connection, the one that's use is the one that's selected in the explorer.
IMHO the bug here is that we're not using the selected connection but the 1st one that exists. I'm updating the description accordingly.)
> Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19845
> URL: https://issues.jboss.org/browse/JBIDE-19845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
>
> If user wants to create a new OpenShift application via context menu of a project, it is possible to do it via context menu "Configure - New/Import OpenShift application". Previously this selection prompted user to choose desired connection where to create a new application. Nowadays the first existing connection in OpenShift explorer view is selected and it is not possible to change connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19845) Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19845?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19845:
------------------------------------------
IMHO we're starting from context menu with a connection (or a domain) selected (otherwise "New->Application" wouldnt show up). Thus it's clear for what connection the user wants to create an application. I tested in JBDS8 and that's how it behaved, you couldnt choose a different connection, the one that's use is the one that's selected in the explorer.
IMHO the bug here is that we're not using the selected connection but the 1st one that exists. I'm updating the description accordingly.
> Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19845
> URL: https://issues.jboss.org/browse/JBIDE-19845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
>
> If user wants to create a new OpenShift application via context menu of a project, it is possible to do it via context menu "Configure - New/Import OpenShift application". Previously this selection prompted user to choose desired connection where to create a new application. Nowadays the first existing connection in OpenShift explorer view is selected and it is not possible to change connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18837.
-------------------------------
Verified with nightly JBT
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: generated-vs-soource-zip.png
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19889?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19889:
------------------------------------------
jenkins is now stable:
{code}
[INFO] openshift.tests .................................... SUCCESS [ 0.391 s]
[INFO] org.jboss.tools.openshift.egit.test ................ SUCCESS [ 20.676 s]
[INFO] org.jboss.tools.openshift.express.test ............. SUCCESS [ 20.341 s]
[INFO] org.jboss.tools.openshift.test ..................... SUCCESS [ 16.585 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:31 min
[INFO] Finished at: 2015-06-01T03:47:15-04:00
[INFO] Final Memory: 64M/689M
[INFO] ------------------------------------------------------------------------
{code}
> Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19889
> URL: https://issues.jboss.org/browse/JBIDE-19889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> I was not cautious enough when merging, the maven build currently fails with the following:
> {code}
> Tests in error:
> LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
> {code}
> {code}
> testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19889?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-19889.
------------------------------------
nothing for QE to verify, closing
> Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19889
> URL: https://issues.jboss.org/browse/JBIDE-19889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> I was not cautious enough when merging, the maven build currently fails with the following:
> {code}
> Tests in error:
> LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
> {code}
> {code}
> testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19889?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19889:
------------------------------------------
easy and quick fix, did it myself.
merged and pushed to upstream/master
> Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19889
> URL: https://issues.jboss.org/browse/JBIDE-19889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
>
> I was not cautious enough when merging, the maven build currently fails with the following:
> {code}
> Tests in error:
> LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
> {code}
> {code}
> testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19889?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19889:
------------------------------------------
[~jcantrill] can you please fix this as one of your very next tasks, since our jenkins is not building any more?
> Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19889
> URL: https://issues.jboss.org/browse/JBIDE-19889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
>
> I was not cautious enough when merging, the maven build currently fails with the following:
> {code}
> Tests in error:
> LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
> {code}
> {code}
> testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19889?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19889:
------------------------------------------
[~jcantrill] can you please fix this as one of your very next tasks, since our jenkins is not building any more?
> Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19889
> URL: https://issues.jboss.org/browse/JBIDE-19889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
>
> I was not cautious enough when merging, the maven build currently fails with the following:
> {code}
> Tests in error:
> LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
> {code}
> {code}
> testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months