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 Apache's JIRA Issue Tracker by Steven Coco, 1 year ago
Parse error reading POM. Reason: only whitespace c ontent allowed before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1)
via apache.org by Unknown author, 2 years ago
Parse error reading POM. Reason: only whitespace c ontent allowed before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1)
via apache.org by Unknown author, 2 years ago
Parse error reading POM. Reason: only whitespace c ontent allowed before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1)
via Google Groups by Unknown author, 9 months ago
Parse error reading POM. Reason: end tag name </project> must match start tag name <oject> from line 1 (position: TEXT seen ...</dependencies>\r\n\r\n</project>... @125:11) for project unknown at /sparehttp://xserve.openqa.org:8080/job/Selenium%20Website/ws/selenium-website/pom.xml
via nabble.com by Unknown author, 2 years ago
Parse error reading POM. Reason: Unrecognised tag: 'plugins' (position: START_TAG seen ...<url>http://www.hjemme.nu</url>\n\n\t<plugins>... @17:11)
org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace content allowed
 before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1)	at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1516)	at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392)	at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090)	at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4545)