Re: problems with xdoc and xalan

2005-03-22 Thread Caoilte O'Connor
o this issue to see what > they should do. > > Cheers. > > Arnaud > > > -Message d'origine- > > De : Kenney Westerhof [mailto:[EMAIL PROTECTED] > > Envoyé : lundi 21 mars 2005 17:48 > > À : Maven Users List > > Objet : Re: problems with xdo

RE: problems with xdoc and xalan

2005-03-21 Thread Arnaud HERITIER
hof [mailto:[EMAIL PROTECTED] > Envoyé : lundi 21 mars 2005 17:48 > À : Maven Users List > Objet : Re: problems with xdoc and xalan > > On Mon, 21 Mar 2005, Caoilte O'Connor wrote: > > Argh, I need to learn how to read better :) > > I think the problem is that

Re: problems with xdoc and xalan

2005-03-21 Thread Kenney Westerhof
On Mon, 21 Mar 2005, Caoilte O'Connor wrote: Argh, I need to learn how to read better :) I think the problem is that you're using jdl 1.5. I've had a lot of trouble myself getting my old projects (using xalan/xerces) to work using jdk 1.5. In jdk 1.4, xerces and xalan are embedded in the jdk. In

Re: problems with xdoc and xalan

2005-03-21 Thread Caoilte O'Connor
On Monday 21 March 2005 15:32, Kenney Westerhof wrote: > You need to set the transformerfactory property before > running ant:style. > > Execute the following jelly script before you call > ant:style: > > ${systemScope.setProperty( >'javax.xml.transform.TransformerFactory', >'org.apache.x

Re: problems with xdoc and xalan

2005-03-21 Thread Kenney Westerhof
On Mon, 21 Mar 2005, Caoilte O'Connor wrote: Hi, You need to set the transformerfactory property before running ant:style. Execute the following jelly script before you call ant:style: ${systemScope.setProperty( 'javax.xml.transform.TransformerFactory', 'org.apache.xalan.processor.Trans

problems with xdoc and xalan

2005-03-21 Thread Caoilte O'Connor
Hi, I'm just starting out with a mavenized project (scarab). I'm familiar with Maven and was just trying to generate documentation (xdoc:transform) but got a pretty nasty error straight off the bat. I'm thinking my JDK setup (Sun 1.5.0) is probably wrong (or possibly my debian/sid ant: 1.6.2)