Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Environment:Sun JDK 1.4, Windows XP
Description
This worked under maven-beta-10. Something must have happened to the XML parser.
I now get the following error generating xdocs:
xdoc:jelly-transform:
[echo] Building HiveModule Registry docs ...
[java] Writing summary for module hivemind
[java] Writing summary for module hivemind
[java] Writing summary for module org.example.bootstrap
[java] Writing summary for module org.example.ui.toolbar
About to use JSL stylesheet file:/C:/Documents and Settings/Howard/.maven/plugins/maven-xdoc-plugin-1.4-SNAPSHOT/plugin-resources/site.jsl
[echo] Generating C:/workspace/hivemind/target/docs/cvs-usage.html from C:\workspace\hivemind\target\generated-xdocs\cvs-usage.xml
[echo] Generating C:/workspace/hivemind/target/docs/dependencies.html from C:\workspace\hivemind\target\generated-xdocs\dependencies.xml
[echo] Generating C:/workspace/hivemind/target/docs/developer-activity-report.html from C:\workspace\hivemind\target\generated-xdocs\developer-activity-report.xml
[echo] Generating C:/workspace/hivemind/target/docs/file-activity-report.html from C:\workspace\hivemind\target\generated-xdocs\file-activity-report.xml
[echo] Generating C:/workspace/hivemind/target/docs/index.html from C:\workspace\hivemind\target\generated-xdocs\index.xml
[echo] Generating C:/workspace/hivemind/target/docs/issue-tracking.html from C:\workspace\hivemind\target\generated-xdocs\issue-tracking.xml
[echo] Generating C:/workspace/hivemind/target/docs/javadoc.html from C:\workspace\hivemind\target\generated-xdocs\javadoc.xml
[echo] Generating C:/workspace/hivemind/target/docs/junit-report.html from C:\workspace\hivemind\target\generated-xdocs\junit-report.xml
[echo] Generating C:/workspace/hivemind/target/docs/mail-lists.html from C:\workspace\hivemind\target\generated-xdocs\mail-lists.xml
[echo] Generating C:/workspace/hivemind/target/docs/maven-reports.html from C:\workspace\hivemind\target\generated-xdocs\maven-reports.xml
[echo] Generating C:/workspace/hivemind/target/docs/project-info.html from C:\workspace\hivemind\target\generated-xdocs\project-info.xml
[echo] Generating C:/workspace/hivemind/target/docs/team-list.html from C:\workspace\hivemind\target\generated-xdocs\team-list.xml
Transforming user supplied documentation.
[echo] Generating C:/workspace/hivemind/target/docs/ant/ConstructRegistry.html from C:\workspace\hivemind\xdocs\ant\ConstructRegistry.xml
[echo] Generating C:/workspace/hivemind/target/docs/ant/index.html from C:\workspace\hivemind\xdocs\ant\index.xml
[echo] Generating C:/workspace/hivemind/target/docs/ant/ManifestClassPath.html from C:\workspace\hivemind\xdocs\ant\ManifestClassPath.xml
[echo] Generating C:/workspace/hivemind/target/docs/bootstrap.html from C:\workspace\hivemind\xdocs\bootstrap.xml
BUILD FAILED
File...... file:/C:/Documents and Settings/Howard/.maven/plugins/maven-xdoc-plugin-1.4-SNAPSHOT/
Element... x:parse
Line...... 328
Column.... 43
C:\workspace\common\links.xml (The system cannot find the path specified) Nested exception: C:\workspace\common\links.xml (The system cannot find the path specified)
Total time: 11 seconds
Finished at: Fri Sep 12 15:35:25 EDT 2003
bootstrap.xml begins with:
<?xml version="1.0"?>
<!-- $Id: bootstrap.xml,v 1.2 2003/09/08 20:14:18 hlship Exp $ -->
<!DOCTYPE document [
<!ENTITY % common-links SYSTEM "../common/links.xml">
%common-links;
]>
<document>
<properties>
<title>Bootstrapping the Registry</title>
<author email="hlship@apache.org">Howard M. Lewis Ship</author>
</properties>
<body>
It contains an external entity, %common-links;. External entities are (to my knowledge) relative to the document, not "the current directory" but Maven appears to be resolving the relative path in terms of "c:\workspace\hivemind" not the correct value "c:\workspace\hivemind\xdoc".
Again, this did work under maven beta-10.
Issue Links
- is superceded by
-
MPXDOC-179
Can't use relative links for external entities
-
This is definitely a regression from dom4j-1.4-dev7 to the released dom4j-1.4.
Copying dom4j-1.4-dev-7.jar over dom4j-1.4.jar resolves the issue