Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Spring JIRA by Matej Spiller-Muys, 1 year ago
expected:<[]\path\to\the\pom\new...> but was:<[C:]\path\to\the\pom\new...>
via Spring JIRA by Matej Spiller-Muys, 2 years ago
expected:<[]\path\to\the\pom\new...> but was:<[C:]\path\to\the\pom\new...>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[4096, vCores:4]>> but was:<<memory:[5120, vCores:5]>>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
via hadoop-yarn-dev by Apache Jenkins Server, 2 years ago
expected:<<memory:[8192, vCores:8]>> but was:<<memory:[4096, vCores:4]>>
org.junit.ComparisonFailure: expected:<[]\path\to\the\pom\new...> but was:<[C:]\path\to\the\pom\new...>	at org.junit.Assert.assertEquals(Assert.java:125)	at org.junit.Assert.assertEquals(Assert.java:147)	at org.springframework.roo.project.MavenPathResolvingStrategyTest.assertIdentifier(MavenPathResolvingStrategyTest.java:76)	at org.springframework.roo.project.MavenPathResolvingStrategyTest.testGetIdentifierForNewModuleWithEmptyRelativePath(MavenPathResolvingStrategyTest.java:97)