Maven 1
  1. Maven 1
  2. MAVEN-156

classpath or jelly:xml issue with XSLT transformations

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0-beta-7
    • Fix Version/s: 1.1-beta-1
    • Component/s: jelly/ant integration
    • Labels:
      None
    • Environment:
      win2k, 1.4.1-b21, maven b7 and also winxp, jdk 1.3.1-01, maven b6
    • Number of attachments :
      0

      Description

      see also my mail to the user list titled 'Style task / x:transform problem'

      It seems there is a general problem with XSLT launched from maven. My own transforms in the maven.xml and that in the docbook plugin behave the same. Behaviour is that instead of transforming as expected the transform command is printed to console. Some processing has occurred (eg var substitution). For example the following:

      <style in="project.xml"
      out="$

      {meta.dir}

      /orion-application.xml"
      style="$

      {code.templates.dir}

      /orion-application.xsl"/>

      prints this to the console:

      <style in="project.xml" out="META-INF/orion-application.xml" style="c:/projects/jdf3/utils/templates/codegen/orion-application.xsl"></style>

      but no transform.

      The same thing results when using x:transform. Other jelly:xml commands such as x:parse and so on work fine

      Using a <java> command to fork a VM and launch a Xalan Process command, taking control of the classpath works ok so I am using this a workaround.

      Hopefully it will be obvious to someone that better understands the way maven loads its classes!

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tim stephenson
            • Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: