-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XSLT warning "The parent axis starting at a document node will never select anything" #859
Comments
Would there be a file associated somewhere in the log with this line and column number? |
Note that there are no Travis checks for Java 11 yet. We should set those up and check if it’s a Java 11 issue. |
I've been looking "everywhere" (EPUBCheck wiki docs, CLI help, known MacOS tmp / app folders, GitHub issue tracker) ... but I am not able to find the full EPUBCheck log. Where should I look for it? Thanks! :) |
I also checked the list of system-level file handles opened/closed by the Java process (MacOS / Darwin), I cannot see any low-level log file. Perhaps there isn't one? In which case, all I have is the log excerpt quoted in my original post (above). |
Sorry I wasn't clear: there's no log file, I was asking if there was more context in the console output from your previous message. Apparently not 😄 |
I added a travis check for JDK 11 with PR #860 but it does not throw any errors like these. So it seems to be an issue with your special book. |
I'm not sure if is related but I'm on a Windows 10 system with the latest version of the source code, java version 1.8 and Maven 3.5.4 and I'm getting a similar behavior. I just did a pull from the repo and did get an update to the travis.yaml file, but no other changes. When I clean and package the code (mvn clean package), I get the exact same message that Daniel is getting when. It is generated by the "com.adobe.epubcheck.api.Epub20CheckExpandedTest" test suite, and even though there are only 22 tests in the set, I see the error 27 times. I have tried this in both the "standard" Windows command prompt and using the Git Bash shell as well; both produce the exact same behavior. I'm just getting started looking at the code base here, and I wasn't sure if this is an expected behavior for that test, but in light of the issue, I wanted to include the information. java version "1.8.0_181" mvn -version |
Thanks for the info, this is helpful. 👍 @danielweck : my understanding was that you got this message when running EpubCheck as a command line, but not during the Maven build itself? Or was it when running the Epub20CheckExpandedTest suite, like @GrayWolfMT? |
and:
Note that "default-test" reports the warning message:
Full console log:
|
With
=>
|
With
=>
|
So, instead of Oracle JDK v11.0.1 from https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html , I have tried with OpenJDK v11.0.1 from https://jdk.java.net/11/
I get the exact same console messages (as detailed above), so I won't repeat them here. Excerpt:
|
I had a fresh look at this issue and I can reproduce it locally too (on macOS 10.13.6 running OpenJDK 11.0.1+13). The issue comes from the schematron XSLT bundled with Jing, which has the Apparently Saxon 9.8 raises a It puzzles me however why the warning doesn't happen on the Travis build… to be further investigated. As for making this warning disappear, we have several options:
I will also file a bug to Jing. |
The Schematron XSLT built in Jing as an `/..` XPath expression which always evaluates to the empty sequence. Saxon 9.8 consequently raises a SXWN9000 warning, when the validators are created (statically, during EPUBCheck's intializations). This PR initalizes Jing's transformer factory with a static error listener that ignores this warning. This is tested as an integration test (since the warning is produced on the standard error stream at initialization time), run via the Maven failsafe plugin. Fixes #859
The Schematron XSLT built in Jing as an `/..` XPath expression which always evaluates to the empty sequence. Saxon 9.8 consequently raises a SXWN9000 warning, when the validators are created (statically, during EPUBCheck's intializations). This PR initalizes Jing's transformer factory with a static error listener that ignores this warning. This is tested as an integration test (since the warning is produced on the standard error stream at initialization time), run via the Maven failsafe plugin. Fixes #859
Hello!
I am on MacOS (latest)
I installed the Oracle JDK (latest v11.0.1 from https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html )
I installed Maven (latest)
I cloned this repository and checkout'ed the
master
branchI invoked the Maven install command (no problems)
I ran EpubCheck from the command line against a few EPUBs (seems to work just fine).
However, the following message is reported over 20 times in the console (just before the actual validation message):
System:
java --version
mvn --version
java -jar target/epubcheck.jar --version
The text was updated successfully, but these errors were encountered: