[ http://issues.apache.org/jira/browse/XALANJ-862?page=all ]

Brian Minchau updated XALANJ-862:
---------------------------------

    Version: Latest Development Code
                 (was: 2.3)

> Tomcat 4 docs build ant style tasks fail with Xalan 2.3.1
> ---------------------------------------------------------
>
>          Key: XALANJ-862
>          URL: http://issues.apache.org/jira/browse/XALANJ-862
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation, Xalan-interpretive
>     Versions: Latest Development Code
>  Environment: Operating System: Solaris
> Platform: Sun
>     Reporter: Glenn Nielsen
>     Assignee: Xalan Developers Mailing List

>
> The Tomcat 4 build of its documentation located in CVS at
> jakarta-tomcat-4.0/webapps/tomcat-docs/build.xml fails frequently 
> when using Xalan 2.3.1. This worked under Xalan 2.2 and 2.2D versions.  
> Here is an example ant style task which is failing, removing the param
> element fixes the problem.  So the problem is related to performing
> multiple transformations using the same stylesheet and passing a parameter
> in.
>     <style basedir="."
>            destdir="${webapps.build}/${webapp.name}"
>          extension=".html"
>              style="tomcat-docs.xsl"
>           excludes="build.xml project.xml"
>           includes="*.xml">
>       <param name="relative-path" expression="."/> 
>     </style>
> I have xercesImpl.jar, xml-apis.jar, and xalan.jar from the 2.3.1 release
> in my classpath.  After it failed the first few times I removed jaxp.jar
> and crimson.jar from the ant installation lib directory, the ant style tasks
> in the build still failed.
> JVM is Java 1.3.1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to