> -----Original Message----- > From: Lukas Theussl [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 08, 2007 7:38 PM > To: Maven Users List > Subject: Re: Xslt in build.xml when run from other dir from > maven gets "Provider for > javax.xml.transform.TransformerFactory cannot be found" > > As far as I can tell from your description, this has nothing > to do with different directories. Just calling ant from maven > is not the same as running ant directly, - classpaths are > different. One solution is to put xalan into > $MAVEN_HOME/lib/endorsed, for the other (prefered), see this FAQ [1].
Ok, setting that system property works, the way it's described in the FAQ. Is it possible to put that setting into the Ant script, and not the Maven script? That Ant target will have to be called from several Maven subprojects, and I'd like to reduce the required boilerplate code. I tried using "sysproperty" in the Ant script, but it didn't have any effect. > Btw, any reason for not using maven 1.1? It's mostly backward > compatible with m1.0.2 [2] and much improved in terms of performance. Good to hear. I don't control our upgrade paths, but I'll mention those two points. > Karr, David wrote: > > JDK 1.4.2, Ant 1.5, Maven 1.0.2. > > > > I developed an Ant script that uses an xslt task. I tested > it in the > > directory where I put it, and it works fine. > > > > I then went to another directory tree managed by maven, and > executed > > some code in my "maven.xml" in a subproject that calls > "ant:ant" and > > calls my build script from the other directory. When I do > this, I get: > > > > Provider for javax.xml.transform.TransformerFactory > cannot be found > > > > I read some notes that indicated that I need to copy "xalan.jar" to > > $ANT_HOME/lib. I don't have it there already, but I do have > > "xml-apis.jar" and "weblogic.jar". > > > > In any case, why does it work directly from the command line in the > > main directory, but fail with that exception when called > from maven in > > the other directory? > > > > Before I implemented the reference to the "xslt" task, the build > > script previously used the "xmltask" library to do the same > thing, and > > that worked well enough, both directly in the build script > directory > > and remotely using maven. I'm trying to get it to work with XSLT > > because the xmltask solution gets OutOfMemory exceptions > for some of > > the larger test cases. > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
