Error: Maven: Non parseable POM ... expected START_TAG or END_TAG not TEXT

So I popped this into eclipse and it looks fine

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>CENSORED</groupId>
    <artifactId>NeoImport</artifactId>
    <version>1.0-SNAPSHOT</version>
    <packaging>jar</packaging>
    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>
    </properties>
    <dependencies>
        <dependency>
            <groupId>org.neo4j.driver</groupId>
            <artifactId>neo4j-java-driver</artifactId>
            <version>1.0.3</version>
        </dependency>
    </dependencies>
</project>

In your screen capture your syntax highlight for the <?xml?> is off at the end. Do you happen to have a newline character before that very first line?

Or if you copied pasted it from somewhere else that formats the text differently than your IDE (i.e. UNIX/OSX vs Dos/Windows) then that may cause issues too.

If you can build your project in your local but you cannot build in Jenkins environment:

• Check if there are any problematic character at the specified line:

Resolution: open your pom file in an editor like np++ to show special characters and removed those characters from your code.

• If not, its Possibly be due to SCM conflicts.

Resolution: Go to Project Build configuration and change the "Check-Out Strategy" within Source Code Management. Use the strategy to first clean checkout instead of just update. Very Likely it should fix the problem that might have arose due to SCM conflicts.