-
Notifications
You must be signed in to change notification settings - Fork 27
Fixes for Maven POM, and a modularization patch #23
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
Conversation
My validator-nu branch contains several patches related to the POM file, and finally a patch for modularization. EDIT: the first patch fixes a broken build for Java 8. Given that the last patch requires JDK 12 or higher, it is not necessary (but does not hurt either). |
One point that I wanted to make: this set of patches includes configuration to build a source and javadoc artifacts, while the previous POM asked to specify that as a command line option (the POM was not set up for that). However, due to a bug in the The section for building the source artifact could be removed though. |
There's several issues with the module descriptor:
|
I did not like exporting a package called
Concerning
It is required but could be changed to a |
I changed |
I added 651e417 — because without it, I get a few dozen errors about javadoc problems:
|
When running
Given that it’s non-fatal and only related to the javadoc build, I don’t think we need to care much about it — but it’d be nice to get rid of that error if we can. Any clues about what might be causing it? |
It is a known bug with a few variants being reported, like: https://issues.apache.org/jira/browse/MJAVADOC-623 In recent years, the production of javadocs with Maven -especially with modular JDKs- is a mess of bugs, with newer versions of We can be happy that with plugin version |
0d7dd39
to
a746a5c
Compare
Also allow `<!-->` at (IE conditional) comment end See whatwg/html#1356 See whatwg/html#1456
Doing `errUnclosedElements(eltPos, "template")` for EOF in the “in template” state results in the error message “End tag `template` seen, but there were open elements”, which is all wrong because the actual problem is that though a `template` end tag was expected, EOF was reached without a `template` end tag being seen. So let’s instead when we reach this just report the list of open elements.
When the parser encounters a `</template>` end tag and there are other open elements, the HTML spec requires the parser to “generate all implied end tags thoroughly”, which unlike “generate implied end tags” also includes generating implied end tags for table-parts elements (caption, colgroup, tbody, thead, tfoot, td, th, and tr).
… C++. Differential Revision: https://phabricator.services.mozilla.com/D82007
This refines 9ce4bd4 by only buffering if we’re actually inside an attribute value.
Fixes #16
a746a5c
to
61325c3
Compare
- Update the file description. - Enforce the usage of UTF-8 encoding (instead of platform-dependent). - Build source and javadoc packages. - Set specific versions for plugins. - Omit the Maven descriptor in the Jar file (which was lost in 2e8c502).
Not required for modularization, but no reason to stay on the old version.
Requires JDK 12 or higher (due to bug in JDK 11), but produces bytecode for Java 7 and 11.
Without this change, the Maven javadoc build fails with fatal errors.
0018e61
to
c37a9da
Compare
c37a9da
to
286cc62
Compare
Fixes: 7b05376