[jira] Commented: (MAVEN-156) classpath or jelly:xml issue with XSLT transformations

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: Juha Komulainen
    Created: Wed, 6 Oct 2004 4:08 AM
       Body:
The above solution does not work on JDK 5.0 at all, where JDK does not include Xalan, but uses XSLTC.

The problem is that when JDK's TransformerFactory tries to load the defined transformer "org.apache.xalan.processor.TransformerFactoryImpl", it doesn't see the classes in Maven's own classloaders, even if plugin has defined Xalan as a dependency.

Fortunately TransformerFactory will try to use Thread's context-classloader instead of system classloader if one is defined. Would it be possible for Maven to set the context classloader to the classloader of the plugin whenever invoking the plugin?
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MAVEN-156?page=comments#action_25013

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-156

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-156
    Summary: classpath or jelly:xml issue with XSLT transformations
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             jelly/ant integration
   Versions:
             1.0-beta-7

   Assignee: 
   Reporter: tim stephenson

    Created: Thu, 21 Nov 2002 5:28 PM
    Updated: Wed, 6 Oct 2004 4:08 AM
Environment: win2k, 1.4.1-b21, maven b7 and also winxp, jdk 1.3.1-01, maven b6

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!


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org