Building FOP Trunk with Ant - BUILD FAILED

[bonekrusher]

Hi,

I am trying to build the FOP trunk (checked out with svn) with Ant and get the following error:

va:231: warning: [deprecation] toURL() in java.io.File has been deprecated
    [javac]                 urls.add(libFiles[i].toURL());
    [javac]                                     ^
    [javac] 26 warnings
    [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
    [javac] Compiling 11 source files to C:\fop_trunk\trunk\build\sandbox-classe
s

resourcegen:
    [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
    [javac] Compiling 3 source files to C:\fop_trunk\trunk\build\codegen-classes

     [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes

BUILD FAILED
C:\fop_trunk\trunk\build.xml:353: java.io.IOException: java.io.FileNotFoundExcep
tion: file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
l (The filename, directory name, or volume label syntax is incorrect)

Total time: 33 seconds

***************************

The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty.

Any thoughts:?

[Peter B. West]

bonekrusher wrote:

> Hi,
>
> I am trying to build the FOP trunk (checked out with svn) with Ant and get
> the following error:
>
> va:231: warning: [deprecation] toURL() in java.io.File has been deprecated
>     [javac]                 urls.add(libFiles[i].toURL());
>     [javac]                                     ^
>     [javac] 26 warnings
>     [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
>     [javac] Compiling 11 source files to
> C:\fop_trunk\trunk\build\sandbox-classe
> s
>
> resourcegen:
>     [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
>     [javac] Compiling 3 source files to
> C:\fop_trunk\trunk\build\codegen-classes
>
>      [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
>
> BUILD FAILED
> C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
> java.io.FileNotFoundExcep
> tion:
> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
> l (The filename, directory name, or volume label syntax is incorrect)
>
> Total time: 33 seconds
>
> ***************************
>
> The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty.
>
> Any thoughts:?

What have you got in lib/build? Have you done an update recently? Fop's
build environment - which has always been challenging - just gets
weirder and weirder.


--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>

[bonekrusher]

I downloaded the latest Trunk this morning, which should be the latest. Correct?

Peter B. West wrote:

bonekrusher wrote:
> Hi,
>
> I am trying to build the FOP trunk (checked out with svn) with Ant and get
> the following error:
>
> va:231: warning: [deprecation] toURL() in java.io.File has been deprecated
>     [javac]                 urls.add(libFiles[i].toURL());
>     [javac]                                     ^
>     [javac] 26 warnings
>     [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
>     [javac] Compiling 11 source files to
> C:\fop_trunk\trunk\build\sandbox-classe
> s
>
> resourcegen:
>     [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
>     [javac] Compiling 3 source files to
> C:\fop_trunk\trunk\build\codegen-classes
>
>      [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
>
> BUILD FAILED
> C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
> java.io.FileNotFoundExcep
> tion:
> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
> l (The filename, directory name, or volume label syntax is incorrect)
>
> Total time: 33 seconds
>
> ***************************
>
> The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty.
>
> Any thoughts:?

What have you got in lib/build? Have you done an update recently? Fop's
build environment - which has always been challenging - just gets
weirder and weirder.


--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>

[Jeremias Maerki-2]

Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
unexpected side-effects.

On 09.07.2008 16:15:54 bonekrusher wrote:
>
> I downloaded the latest Trunk this morning, which should be the latest.
> Correct?
<snip/>



Jeremias Maerki

[Adrian Cumiskey]

Looks like your generated file URL has been somehow escaped incorrectly, not sure that would work....

"file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml"

Which version of Java are you using and on which Windows platform?

Adrian.

bonekrusher wrote:

> I downloaded the latest Trunk this morning, which should be the latest.
> Correct?
>
>
> Peter B. West wrote:
>> bonekrusher wrote:
>>> Hi,
>>>
>>> I am trying to build the FOP trunk (checked out with svn) with Ant and
>>> get
>>> the following error:
>>>
>>> va:231: warning: [deprecation] toURL() in java.io.File has been
>>> deprecated
>>>     [javac]                 urls.add(libFiles[i].toURL());
>>>     [javac]                                     ^
>>>     [javac] 26 warnings
>>>     [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
>>>     [javac] Compiling 11 source files to
>>> C:\fop_trunk\trunk\build\sandbox-classe
>>> s
>>>
>>> resourcegen:
>>>     [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
>>>     [javac] Compiling 3 source files to
>>> C:\fop_trunk\trunk\build\codegen-classes
>>>
>>>      [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes
>>>
>>> BUILD FAILED
>>> C:\fop_trunk\trunk\build.xml:353: java.io.IOException:
>>> java.io.FileNotFoundExcep
>>> tion:
>>> file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
>>> l (The filename, directory name, or volume label syntax is incorrect)
>>>
>>> Total time: 33 seconds
>>>
>>> ***************************
>>>
>>> The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is
>>> empty.
>>>
>>> Any thoughts:?
>> What have you got in lib/build? Have you done an update recently? Fop's
>> build environment - which has always been challenging - just gets
>> weirder and weirder.
>>
>>
>> --
>> Peter B. West <http://cv.pbw.id.au/>
>> Folio <http://defoe.sourceforge.net/folio/>
>>
>>
>

[bonekrusher]

Jeremias - thanks, that did the trick.

Now I am on to see if I can fix the table-continued implementation. Wish me luck :)

Regards,

Jeremias Maerki-2 wrote:

Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
unexpected side-effects.

On 09.07.2008 16:15:54 bonekrusher wrote:
>
> I downloaded the latest Trunk this morning, which should be the latest.
> Correct?
<snip/>



Jeremias Maerki

[bonekrusher]

I spoke to soon. I am getting the same error after the clean.

I am using Java 1.6

Any ideas?

thx

Jeremias Maerki-2 wrote:

Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
unexpected side-effects.

On 09.07.2008 16:15:54 bonekrusher wrote:
>
> I downloaded the latest Trunk this morning, which should be the latest.
> Correct?
<snip/>



Jeremias Maerki

[Jeremias Maerki-2]

Not really. Please do "ant clean package >out.txt" and send me the
"out.txt" file (off-list).

On 09.07.2008 16:45:48 bonekrusher wrote:

>
> I spoke to soon. I am getting the same error after the clean.
>
> I am using Java 1.6
>
> Any ideas?
>
> thx
>
>
> Jeremias Maerki-2 wrote:
> >
> > Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
> > wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
> > unexpected side-effects.
> >
> > On 09.07.2008 16:15:54 bonekrusher wrote:
> >>
> >> I downloaded the latest Trunk this morning, which should be the latest.
> >> Correct?
> > <snip/>
> >
> >
> >
> > Jeremias Maerki
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html
> Sent from the FOP - Dev mailing list archive at Nabble.com.

Jeremias Maerki

[bonekrusher]

Hi  Jeremias - I set you an email. Let me know if you received it. thx

Jeremias Maerki-2 wrote:

Not really. Please do "ant clean package >out.txt" and send me the
"out.txt" file (off-list).

On 09.07.2008 16:45:48 bonekrusher wrote:
>
> I spoke to soon. I am getting the same error after the clean.
>
> I am using Java 1.6
>
> Any ideas?
>
> thx
>
>
> Jeremias Maerki-2 wrote:
> >
> > Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
> > wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
> > unexpected side-effects.
> >
> > On 09.07.2008 16:15:54 bonekrusher wrote:
> >>
> >> I downloaded the latest Trunk this morning, which should be the latest.
> >> Correct?
> > <snip/>
> >
> >
> >
> > Jeremias Maerki
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html
> Sent from the FOP - Dev mailing list archive at Nabble.com.




Jeremias Maerki

[Leeloo5E-Devel]

Hi,

got the same problem when trying to build FOP from Trunk with the pre-installed version 1.6.5 of ant on a linux maschine. Using version 1.7.0 instead, the build runs fine. I do not try the newest version 1.7.1 of ant yet (I comes out on june 28th). For building FOP from Trunk I used the pre-installed jre 1.4.2 or 1.5.0 from SUN on my linux maschines.

Thats my suggestions.

Best Regards,
Lee

bonekrusher wrote:

Hi,

I am trying to build the FOP trunk (checked out with svn) with Ant and get the following error:

va:231: warning: [deprecation] toURL() in java.io.File has been deprecated
    [javac]                 urls.add(libFiles[i].toURL());
    [javac]                                     ^
    [javac] 26 warnings
    [mkdir] Created dir: C:\fop_trunk\trunk\build\sandbox-classes
    [javac] Compiling 11 source files to C:\fop_trunk\trunk\build\sandbox-classe
s

resourcegen:
    [mkdir] Created dir: C:\fop_trunk\trunk\build\codegen-classes
    [javac] Compiling 3 source files to C:\fop_trunk\trunk\build\codegen-classes

     [copy] Copying 2 files to C:\fop_trunk\trunk\build\codegen-classes

BUILD FAILED
C:\fop_trunk\trunk\build.xml:353: java.io.IOException: java.io.FileNotFoundExcep
tion: file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xm
l (The filename, directory name, or volume label syntax is incorrect)

Total time: 33 seconds

***************************

The C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events folder is empty.

Any thoughts:?

[Jeremias Maerki-2]

Bonekrusher and I had an exchange off-list. He did a few tests for me
and my recent change didn't help either.

Basically, we established the following:
- He's also running WinXP
- He's running the same JDK as I do.
- The XSLT processor used in the context of the error is a normal Apache
Xalan, just like on my machine.

I think Adrian's comment (about the file URL) could be a good hint at
what's wrong but I have no idea where this is coming from. Short of
debugging the code on Bonekrusher's machine I have no idea how to fix
this problem.

On 09.07.2008 19:58:20 bonekrusher wrote:

>
> Hi  Jeremias - I set you an email. Let me know if you received it. thx
>
>
> Jeremias Maerki-2 wrote:
> >
> > Not really. Please do "ant clean package >out.txt" and send me the
> > "out.txt" file (off-list).
> >
> > On 09.07.2008 16:45:48 bonekrusher wrote:
> >>
> >> I spoke to soon. I am getting the same error after the clean.
> >>
> >> I am using Java 1.6
> >>
> >> Any ideas?
> >>
> >> thx
> >>
> >>
> >> Jeremias Maerki-2 wrote:
> >> >
> >> > Yes. Works fine for me, BTW. An "ant clean" prior to the build can work
> >> > wonders sometimes. Also, make sure you're using a Sun JVM to avoid any
> >> > unexpected side-effects.
> >> >
> >> > On 09.07.2008 16:15:54 bonekrusher wrote:
> >> >>
> >> >> I downloaded the latest Trunk this morning, which should be the
> >> latest.
> >> >> Correct?
> >> > <snip/>
> >> >
> >> >
> >> >
> >> > Jeremias Maerki
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18363253.html
> >> Sent from the FOP - Dev mailing list archive at Nabble.com.
> >
> >
> >
> >
> > Jeremias Maerki
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18367327.html
> Sent from the FOP - Dev mailing list archive at Nabble.com.

Jeremias Maerki

[Andreas Delmelle-2]

On Jul 11, 2008, at 13:22, Jeremias Maerki wrote:

> Bonekrusher and I had an exchange off-list. He did a few tests for me
> and my recent change didn't help either.
>
> Basically, we established the following:
> - He's also running WinXP
> - He's running the same JDK as I do.

The /exact/ same one (identical build)?

Just asking, since I remember running across some issues/
inconsistencies in the way the java.net.URL and java.net.URI  
translate themselves to a String.
Maybe that's what's playing here... Is the warning about the  
deprecated File.toURL() maybe related and a hint?

As of Java 6, the recommended way is to use File.toURI().toURL().  
According to the API docs, File.toURL() "does not automatically  
escape characters that are illegal in URLs. It is recommended that  
new code convert an abstract pathname into a URL by first converting  
it into a URI, via the toURI method, and then converting the URI into  
a URL via the URI.toURL method."

Makes you wonder why the implementation of toURL() then does not  
simply do that already... I assume this is for reasons of backward-
compatibility, so as to not break any existing code that relies on  
that behavior (?)



Cheers

Andreas

[Jeremias Maerki-2]

On 12.07.2008 11:56:23 Andreas Delmelle wrote:

> On Jul 11, 2008, at 13:22, Jeremias Maerki wrote:
>
> > Bonekrusher and I had an exchange off-list. He did a few tests for me
> > and my recent change didn't help either.
> >
> > Basically, we established the following:
> > - He's also running WinXP
> > - He's running the same JDK as I do.
>
> The /exact/ same one (identical build)?

Yes, Sun 1.6.0_04

>
> Just asking, since I remember running across some issues/
> inconsistencies in the way the java.net.URL and java.net.URI  
> translate themselves to a String.
> Maybe that's what's playing here... Is the warning about the  
> deprecated File.toURL() maybe related and a hint?

If it is in fact the file URL that's the problem, I'm pretty sure the
problem happens within Xalan as I'm passing in a StreamResult(File).

> As of Java 6, the recommended way is to use File.toURI().toURL().  
> According to the API docs, File.toURL() "does not automatically  
> escape characters that are illegal in URLs. It is recommended that  
> new code convert an abstract pathname into a URL by first converting  
> it into a URI, via the toURI method, and then converting the URI into  
> a URL via the URI.toURL method."

I guess it makes sense to change all occurences now that we're on Java
1.4. I've changed the StreamSource(File) to
StreamSource(File.toURI().toURL().toExternalForm()) as a first
experiment. Bonekrusher can then retry on his machine.
http://svn.apache.org/viewvc?rev=676161&view=rev

On my machine the following:
        System.out.println(outputFile.toURI().toASCIIString());
        System.out.println(outputFile.toURI().toString());
        System.out.println(outputFile.toURI().toURL().toExternalForm());
        System.out.println(outputFile.toURL().toExternalForm());
yielded the following results:
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml

Just for reference, Bonekrusher got
file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml
on his machine (see his first post).

> Makes you wonder why the implementation of toURL() then does not  
> simply do that already... I assume this is for reasons of backward-
> compatibility, so as to not break any existing code that relies on  
> that behavior (?)

Probably.

>
>
> Cheers
>
> Andreas




Jeremias Maerki

[bonekrusher]

Ok, I wanted to test this at home to see if this was a machine issue.

Tested on:

Windows XP sp2
Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)

I am still unable to build with ant. I get another set of errors.

I will email Jeremias the out.txt file.

I also tried the the version (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a bunch of errors. I will send that report to.

Bones

Jeremias Maerki-2 wrote:

On 12.07.2008 11:56:23 Andreas Delmelle wrote:
> On Jul 11, 2008, at 13:22, Jeremias Maerki wrote:
>
> > Bonekrusher and I had an exchange off-list. He did a few tests for me
> > and my recent change didn't help either.
> >
> > Basically, we established the following:
> > - He's also running WinXP
> > - He's running the same JDK as I do.
>
> The /exact/ same one (identical build)?

Yes, Sun 1.6.0_04

>
> Just asking, since I remember running across some issues/
> inconsistencies in the way the java.net.URL and java.net.URI  
> translate themselves to a String.
> Maybe that's what's playing here... Is the warning about the  
> deprecated File.toURL() maybe related and a hint?

If it is in fact the file URL that's the problem, I'm pretty sure the
problem happens within Xalan as I'm passing in a StreamResult(File).

> As of Java 6, the recommended way is to use File.toURI().toURL().  
> According to the API docs, File.toURL() "does not automatically  
> escape characters that are illegal in URLs. It is recommended that  
> new code convert an abstract pathname into a URL by first converting  
> it into a URI, via the toURI method, and then converting the URI into  
> a URL via the URI.toURL method."

I guess it makes sense to change all occurences now that we're on Java
1.4. I've changed the StreamSource(File) to
StreamSource(File.toURI().toURL().toExternalForm()) as a first
experiment. Bonekrusher can then retry on his machine.
http://svn.apache.org/viewvc?rev=676161&view=rev

On my machine the following:
        System.out.println(outputFile.toURI().toASCIIString());
        System.out.println(outputFile.toURI().toString());
        System.out.println(outputFile.toURI().toURL().toExternalForm());
        System.out.println(outputFile.toURL().toExternalForm());
yielded the following results:
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml
[eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml

Just for reference, Bonekrusher got
file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml
on his machine (see his first post).

> Makes you wonder why the implementation of toURL() then does not  
> simply do that already... I assume this is for reasons of backward-
> compatibility, so as to not break any existing code that relies on  
> that behavior (?)

Probably.

>
>
> Cheers
>
> Andreas




Jeremias Maerki

[Andreas Delmelle-2]

On Jul 13, 2008, at 13:23, bonekrusher wrote:

>
> Ok, I wanted to test this at home to see if this was a machine issue.

Just out of curiosity, can you try to copy the following files under %
FOP%/lib :

serializer-2.7.0.jar
xalan-2.7.0.jar
xercesImpl-2.7.1.jar
xml-apis-1.3.04.jar

to the lib/endorsed directory in the Java home dir (create if it does  
not exist).

Then try to run the clean build again.

It's a long shot, but maybe if the Xerces/Xalan implementations are  
forced to be the same ones that FOP ships with...


HTH!

Cheers

Andreas

[Peter B. West]

bonekrusher wrote:

> Ok, I wanted to test this at home to see if this was a machine issue.
>
> Tested on:
>
> Windows XP sp2
> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>
> I am still unable to build with ant. I get another set of errors.
>
> I will email Jeremias the out.txt file.
>
> I also tried the the version
> (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a
> bunch of errors. I will send that report to.
>
> Bones
>

What does
  ant -version
tell you?

How do you find out which command is being executed in Windows? In
linux, you execute
  which ant
or
  type ant

Can you do the equivalent on your system.

Can you list the files and file sizes of lib and lib/build?

--
Peter B. West <http://cv.pbw.id.au/>
Folio <http://defoe.sourceforge.net/folio/>

[Andreas Delmelle-2]

On Jul 13, 2008, at 14:04, Peter B. West wrote:

> bonekrusher wrote:
>> Ok, I wanted to test this at home to see if this was a machine issue.
>> Tested on:
>> Windows XP sp2
>> Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12)
>> Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing)
>> I am still unable to build with ant. I get another set of errors.
>> I will email Jeremias the out.txt file.
>> I also tried the the version
>> (src/java/org/apache/fop/events/model/EventModel.java) posted, but  
>> got a
>> bunch of errors. I will send that report to.
>> Bones
>
> What does
>  ant -version
> tell you?
>
> How do you find out which command is being executed in Windows? In  
> linux, you execute
>  which ant

Come to think of it, also check whether there is a JAVACMD  
environment variable that points to a java executable in a location  
other than JAVA_HOME/bin.
In that case, the Java home echoed by the build script may throw one  
off course in determining the version of Java that is actually used.


Cheers

Andreas