> Sorry, I was a bit misleading. The XSLT question in the FAQ alludes to it,
> but the actuall documentation I was referring to is at the bottom of the
> developers guide :)
Well, finally, I've found that guide. :)
>
> Basically, try adding this to your saxon dependency:
> <properties>
> <classloader>maven</classloader>
> </properties>
>
I tried this, but it does not work too.
Now I have the following in my dependencies:
<dependency>
<id>saxon</id>
<version>7.6.5</version>
<properties>
<classloader>root</classloader>
</properties>
</dependency>
<dependency>
<id>saxon-jdom</id>
<version>7.6.5</version>
<properties>
<classloader>root</classloader>
</properties>
</dependency>
And my project.properties:
maven.jar.override = on
maven.jar.saxon = ${basedir}/lib/saxon7.jar
maven.jar.saxon-jdom = ${basedir}/lib/saxon7-jdom.jar
> Alternatively, put saxon in your $CLASSPATH variable before starting - but
> that could lead to more problems.
>
I tried that way too, with the same result. It seems for me that this is a
<j:include/>
problem.
> Location of XML parsers are the bane of the Java developers existence
these
> days...
I can understand that. What I can't understand is why script included via
<j:include/> does
not see saxon jars?
--
Best regards
Pavel Sher [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
