An error Maven with linkchecker | Community
Skip to main content
W
wmakend
New Participant
October 16, 2015
Solved

An error Maven with linkchecker

  • October 16, 2015
  • 17 replies
  • 6027 views
When I deploy my source I get this message below. I do not understand why I see the linkchecker------ Caused by: org.apache.maven.plugin.MojoExecutionException: end tag name </td> must match start tag name <img> from line 31 (position: START_TAG seen ...="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0"></td>... @31:243) 
        at com.day.jcr.vault.maven.mgr.AbstractPackageManagerMojo.postRequest(AbstractPackageManagerMojo.java:261)
        at com.day.jcr.vault.maven.mgr.PackageInstallMojo.uploadPackage(PackageInstallMojo.java:267)
        at com.day.jcr.vault.maven.mgr.PackageInstallMojo.execute(PackageInstallMojo.java:200)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        ... 31 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name </td> must match start tag name <img> from line 31 (position: START_TAG seen ...="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0"></td>... @31:243) 
        at org.codehaus.plexus.util.xml.pull.MXParser.parseEndTag(MXParser.java:1689)
        at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1172)
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

it has to do with the POST request issued by the content-package-plugin, as it is indicated by this line

Caused by: org.apache.maven.plugin.MojoExecutionException: end tag name </td> must match start tag name <img> from line 31 (position: START_TAG seen ...="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0"></td>... @31:243) at com.day.jcr.vault.maven.mgr.AbstractPackageManagerMojo.postRequest(AbstractPackageManagerMojo.java:261)

as then the XML parser is listed as the root cause of this exception, my assumption is that the content-package-maven-plugin utilizes an XML parser to parse the output of the POST request, but then somehow fails. It would be good if you sniff the network trafic in that case, so we actually know what's happening. Also the request.log can give insight what status code is sent for this POST request.

kind regards,
Jörg

17 replies

Feike_Visser1
Feike_Visser1
Employee
September 1, 2016

Anyway you can share a sample here, then we can have at it.

Best guess now is that there is something a typo.

D
dannys23048637
New Participant
September 1, 2016

The problem is not with the plugin itself but rather on AEM. After installing the first package with a jar file, AEM restarts most of the bundles including the ones to handle package installation. Therefore AEM is not ready to have a package installed and would need to wait for a while before it can accept another package.

Tyler_Maynard
Tyler_Maynard
New Participant
August 31, 2016

We still get this from time to time. Is there an updated version of  Content-Package-Maven-Plugin that resolves this? It looks like we are on .0.0.24 and version 0.5.21 is available... Does anyone know if that successfully resolves the issue? 

https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/

D
dannys23048637
New Participant
June 8, 2016

Seems like the root cause was the server was still in the process of re-registering the services for installing via maven that was un-registered when the previous package was installed. I resolved it by added some delays to install the next package to give the server enough time to re-register the service by using maven-antrun-plugin

joerghoh
joerghoh
Employee
May 13, 2016

Hi

the problem is that the AEM instance throws an error when maven tries to upload the file to AEM. Please check your AEM logs to find out what's the root cause exactly.

Jörg

D
dannys23048637
New Participant
May 13, 2016

Hi guys,

I know this is an old thread but we are having the same issue for our project. Anyone kind enough to post the solution to this issue? This is happening intermittently and is causing some issues to our project builds. Perhaps there is a way to disable fail on xml error?

A
Anonymous
October 23, 2015

So what fixed it for you, wmakend?

smacdonald2008
smacdonald2008
New Participant
October 23, 2015

The user who opened this thread says problem was solved. 

A
Anonymous
October 23, 2015
This was wrongfully closed. The problem was not solved.

In the 2 links edubey posted, the roots of the problem are in the pom or repository.

 

But here it seems not to be a problem of maven, but more a problem of AEM.

It occurs when trying to deploy the module that fails:

ERROR] Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:0.0.24:install (install-content-package) on project global-skizz_1.4.0-i18n: end tag name </td> must match start tag name <img> from line 31 (position: START_TAG seen ...="/libs/cq/linkchecker/resources/linkcheck_c.gif" border="0"></td>... @31:243) -> [Help 1]

 

"grep"-ing through our Code for "linkcheck" shows no result at all. So I guess, this is a (incomplete) response from AEM.

Taking a tcpdump of the communication between "mvn" and "AEM", shows nothing abnormal.

 

Kind regards,

 

Jerry

smacdonald2008
smacdonald2008
New Participant
October 16, 2015

There is a mismatch in your code. Look at the exception - it giving you a hint at line 31 in your code. 

"end tag name </td> must match start tag name <img> from line 31"
Show more replies
Terms & ConditionsAccessibility statement

Loading footer...