Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Maven generate-sources HtmlPolicy
See original GitHub issueHi,
is it possible to use a custom HtmlPolicy when using the maven plugin to generate sources during build?
I want to package the templates with my application (like this: https://github.com/casid/jte/blob/master/DOCUMENTATION.md#using-the-application-class-loader-since-120)
As I am using Html Attributes without a value for testing (i.e. <div data-test-important-content>) I have to use a custom policy. Unfortunately my build is breaking because of the failed policy:
Failed to execute goal gg.jte:jte-maven-plugin:1.5.0:generate (default) on project service-frontend:
Execution default of goal gg.jte:jte-maven-plugin:1.5.0:generate failed:
Failed to compile tag/shop/communication.jte, error at line 1: Unquoted HTML attribute values are not allowed: data-test-shop-communication
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Fender123 Unquoted attributes without value should be allowed for all attributes, so e.g.
<input disabled>should be allowed, too.The feature is intended to make the automatic attribute escaping less complex by not having to support various escaping mechanism based on quoting. If attributes do not contain variables, it’s probably OK to allow those, too, so e.g.
<input value=foo>, but AFAIK most people default to quoting always.ok, thanks for the clarification.
Yes I experienced same strange hot reloading behavior, but not always…
Maybe I should have a look into CompilerMojo as well.