Re: Building FOP Trunk with Any - BUILD FAILED

[Bones]

Well, I am too. My advise is to put this issue on the the back burner and see
if anyone can duplicate the problem. 

thoughts?

Andreas Delmelle-2 wrote:
> 
> On Jul 16, 2008, at 13:00, Bones wrote:
> 
> Hi Phil
> 
>>
>> My parser/transform environment is the standard which comes with FOP,
>> however when I use FOP for development I also use SAXON for  
>> transformation
>> and sometimes pure Sax2 for parsing. It depends.
> 
> I haven't yet encountered such issues when /running/ FOP, only when  
> building.
> If you only use FOP, this shouldn't really pose a problem. Seen that  
> you're eager to start developing, it is a rather unfortunate one... :-/
> 
> BTW: Remember also that, when running FOP, unless you explicitly  
> force the JVM to use the Xerces and Xalan versions in the  
> distribution, then it will use whatever XML parser and XSLT processor  
> come first in the classpath (most JVMs come bundled with a fallback  
> parser; some, like GNU Classpath, do not have an XSLT processor,  
> which causes mayhem in some environments because Xalan does not work  
> in combination with the GNU XML parser...)
> 
>> "In the end, I got it working by making sure that the build process
>> was using the exact same XML parser and XSLT processor that were
>> distributed with FOP. " - How do I do that with in ant?
>>
> 
> 
> Basically the same as for every other java application, it comes down  
> to either:
> 
> * copying all necessary JARs to JAVA_HOME/lib/endorsed
> * prepending those JARs to the bootclasspath (as in: "java - 
> Xbootclasspath/p:...")
> * specifying the exact implementations to use by passing Java system  
> properties (pattern: -Dinterface=implementation, as in: "java - 
> Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryI 
> mpl ...")
> 
> The latter two options, for Ant, work by setting the ANT_OPTS  
> environment variable (see: http://ant.apache.org/manual/ 
> running.html#envvars)
> 
> The first I already hinted at earlier, and you said you had tried it,  
> to no avail, so I'm quite clueless at the moment. :-S
> 
> 
> Cheers
> 
> Andreas
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18493995.html
Sent from the FOP - Dev mailing list archive at Nabble.com.

Re: Building FOP Trunk with Any - BUILD FAILED

[Bones]

"In the end, I got it working by making sure that the build process  
was using the exact same XML parser and XSLT processor that were  
distributed with FOP. " - How do I do that with in ant?




Peter B. West wrote:
> 
> Andreas Delmelle wrote:
>> On Jul 15, 2008, at 14:55, Chris Bowditch wrote:
>> 
>>> bonekrusher wrote:
>>>
>>> Hi,
>>>
 Thanks Peter. 
 C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml 
 This file is missing.
>>>
>>> That file is created by the build process. I think Peter was talking 
>>> about how the build process references the file internally.
>> 
>> Yeah, but after so many builds, one would assume that the file would 
>> have been generated in the meantime.
>> 
> 
> Yes, that's what I'm thinking.
> 
>> I had similar issues after the introduction of the event-module (but 
>> those were NPEs, because the above mentioned file was not correctly 
>> generated).
>> In the end, I got it working by making sure that the build process was 
>> using the exact same XML parser and XSLT processor that were distributed 
>> with FOP.
> 
> The transformation process probably needs to be made more robust.
> 
> Phil, what's your parser/transform environment?
> -- 
> Peter B. West 
> Folio 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18485057.html
Sent from the FOP - Dev mailing list archive at Nabble.com.

Re: Building FOP Trunk with Any - BUILD FAILED

[Bones]

Hi Andreas,

My parser/transform environment is the standard which comes with FOP,
however when I use FOP for development I also use SAXON for transformation
and sometimes pure Sax2 for parsing. It depends.

Phil

Peter B. West wrote:
> 
> Andreas Delmelle wrote:
>> On Jul 15, 2008, at 14:55, Chris Bowditch wrote:
>> 
>>> bonekrusher wrote:
>>>
>>> Hi,
>>>
 Thanks Peter. 
 C:\foptrunk2\trunk\build\gensrc\org\apache\fop\events\event-model.xml 
 This file is missing.
>>>
>>> That file is created by the build process. I think Peter was talking 
>>> about how the build process references the file internally.
>> 
>> Yeah, but after so many builds, one would assume that the file would 
>> have been generated in the meantime.
>> 
> 
> Yes, that's what I'm thinking.
> 
>> I had similar issues after the introduction of the event-module (but 
>> those were NPEs, because the above mentioned file was not correctly 
>> generated).
>> In the end, I got it working by making sure that the build process was 
>> using the exact same XML parser and XSLT processor that were distributed 
>> with FOP.
> 
> The transformation process probably needs to be made more robust.
> 
> Phil, what's your parser/transform environment?
> -- 
> Peter B. West 
> Folio 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18485037.html
Sent from the FOP - Dev mailing list archive at Nabble.com.