"Jacob Kjome" wrote on 11/12/2010 01:29:38 PM:
> Why wouldn't source and target be hardcoded in the build? Xerces source
> compliance is not a dynamic thing. It should be hardcoded in the build
to
> whatever is level Xerces advertises it to be.
Except that there's isn't just one level. There
Why wouldn't source and target be hardcoded in the build? Xerces source
compliance is not a dynamic thing. It should be hardcoded in the build to
whatever is level Xerces advertises it to be. According to the Java docs [1]
the default behavior is (assuming you hardcode -source)
"If -sou
Eric Smith wrote on 11/11/2010 04:10:54 PM:
> Hi,
>
> When I try to build Xerces-J with gcj as my jdk, it fails with
>
> compile:
> [copy] Copying 23 files to
> /var/tmp/paludis/build/dev-java-Xerces-J-2.10.0/work/xerces-2_10_0/
> build/classes
> [xjavac] Compiling 704 source files to
> /var/tmp/
