Hello Builds,
We are still seeing this error. It just occurred a few minutes ago on jenkins-test-d2e. https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-JoramJMSTest/jdk=latest1.7,label=Ubuntu,qpid.joramtests=qpid-jms-client/497/ [trunk] $ /home/jenkins/tools/maven/apache-maven-3.0.4/bin/mvn -f pom.xml -Dlabel=Ubuntu -Djdk=latest1.7 -Dqpid.joramtests=qpid-jms-client -DskipTests=true clean verify -fae [ERROR] Error executing Maven. [ERROR] 1 problem was encountered while building the effective settings [FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected character in markup % (position: START_TAG seen ...</username>\n <password><%... @14:18) @ /home/jenkins/.m2/settings.xml, line 14, column 18 Build step 'Invoke top-level Maven targets' marked build as failure On 3 June 2016 at 09:16, Keith W <keith.w...@gmail.com> wrote: > Hello builds > > We (Apache Qpid) are seeing failures on Jenkins ubuntu-4 with the > following error for the last few builds. > > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-JoramJMSTest/494/ > > The job doesn't knowingly try to influence the contents of this file, > so I suspect something else has caused the file to become corrupted. > > Could someone take a look? > > No changes for http://svn.apache.org/repos/asf/qpid/java/trunk since > the previous build > [trunk] $ /home/jenkins/tools/maven/apache-maven-3.0.4/bin/mvn -f > pom.xml -Dlabel=Ubuntu -Djdk=latest1.7 > -Dqpid.joramtests=qpid-amqp-1-0-client-jms -DskipTests=true clean > verify -fae > [ERROR] Error executing Maven. > [ERROR] 1 problem was encountered while building the effective settings > [FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: > unexpected character in markup % (position: START_TAG seen > ...</username>\n <password><%... @14:18) @ > /home/jenkins/.m2/settings.xml, line 14, column 18 > > Kind regards, Keith Wall.
