Uploaded image for project: 'Maven Doxia'
  1. Maven Doxia
  2. DOXIA-440

Unable to place XML in <source> in FML

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Module - Fml
    • Labels:
      None
    • Environment:
      maven-site-plugin 3.0
      Mac OS X Lion
      Java 6 Update 26, Maven 3.0.3

      Description

      I have a faq.fml.vm file that has XML embedded in a <source> tag like this:

      <?xml version="1.0" encoding="UTF-8"?>
      <faqs id="FAQ" title="Frequently Asked Questions">
        <part id="General">
          <title>General</title>
          <faq id="needed">
            <question>Is the question important?</question>
            <answer>
              <p>No.  I am merely trying to illustrate that I can't render XML correctly as part of the <em>source</em> tag.</p>
              <source>
      <dependencies>
        <dependency>
          <groupId>org.projectlombok</groupId>
          <artifactId>lombok</artifactId>
          <version>${LombokVersion}</version>
          <scope>provided</scope>
        </dependency>
      </dependencies>
              </source>
            </answer>
          </faq>
        </part>
      </faqs>
      

      Note that this used to display correctly with Maven2/Site2.x... (I haven't isolated precisely what was changed to break this.)

      If there is a bug in my FML, then I suggest tweaking the documentation to include this case as I could not find documentation explaining how to do this.

      Thanks!

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              awhitford Anthony Whitford

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment