[
http://jira.codehaus.org/browse/MPLUGIN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136687#action_136687
]
Guimiot Isabelle commented on MPLUGIN-119:
------------------------------------------
Thanks for your comments, you're right, I had the plugin-plugin version set in
the reporting tag, but nothing in the build tag. Now, it works fine !
> Regression when generating site (mojo description pages) for my own maven
> plugins
> ---------------------------------------------------------------------------------
>
> Key: MPLUGIN-119
> URL: http://jira.codehaus.org/browse/MPLUGIN-119
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API, Plugin Plugin
> Affects Versions: 2.4
> Environment: ms windows
> Reporter: Guimiot Isabelle
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 2.4.2
>
>
> I have developped several maven plugins for my project, and each time I
> deliver a new version, I generate the plugin site, with mojo pages
> (xxx-mojo.html) describing each goal and its parameters.
> The description found in these pages is based on the javadoc that I wrote in
> my java mojo classes, and as I'm french, I use accents in my javadoc (java
> source code encoded in ISO-8859-1). The generation has 2 steps : first, an
> xdoc file is created in target/generated-site/xdoc, and second, the html file
> is generated from the xdoc.
> When I was using maven 2.0.8 and older versions, the xdoc was containing real
> accents and I had no problem during the build, and the html file was good.
> Now, with maven 2.0.9, the xdoc contains "& eacute;" characters instead of
> accents, and when the build generates the site, this exception is raising :
> [ERROR] Error parsing
> C:\wks\maven-mypersonal-plugin\target\generated-site\xdoc\mypersonalgoal-mojo.xml:
> line [-1] Error parsing the model.
> org.apache.maven.doxia.parser.ParseException: Error parsing the model.
> at
> org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:55)
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:52)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:264)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:43)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:132)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: could
> not resolve entity named 'eacute' (position: START_TAG seen ...<p>Ce goal
> supprime le contenu du ré... @11:50)
> at
> org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1282)
> at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1093)
> at
> org.apache.maven.doxia.module.xdoc.XdocParser.parseXdoc(XdocParser.java:312)
> at
> org.apache.maven.doxia.module.xdoc.XdocParser.parse(XdocParser.java:51)
> ... 25 more
> It's a minor bug, because it only happens when I call "mvn install site" in a
> single mvn command. When I first launch "mvn install", and then "mvn site",
> it works fine ! I really don't know why...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
