Repository navigation
Web component support - #211
Conversation
- Several elements have been found to be missing from the code generator. - A long-term strategy for dealing with obsolete elements will be needed. Should we remove and change the API? Or should we deprecate and leave in-place? - Found one element that was accidentally added to the code generator but never used. Hopefully. - Fixes will be applied in following commits.
- Added DataTag. - Added SlotTag and TemplateTag to support web components. - Added global attributes to support web components. - Removed GenerateTag. Accidentally introduced by string replacement in code generator.
…l of GenerateTag. - The GenerateTag class was created accidentally. It does not have any representation in the HTML standard is should not be provided in this library.
|
|
|
What is this giant |
|
The |
|
No, it's not an issue, it's just very large. So you want 1.6.0 released after this is merged? |
|
Yes, it would be good to complete some open issues and signal that the project isn't dead with 1.6.0. |
|
|
Looks like upgrading the plugin might fix that. Check #213 to see if that works. |
|
Thanks @sembler ! That did get me a step further, currently I'm stuck on: |
|
Maybe this error isn't showing up for me because I'm running the build on 1.8.0_322? I'll investigate. Edit: Yes, it was the JDK version. I'll see if the plugin can be made to work on both versions, or if we'll need to focus on one JDK. |
|
Thanks, let me know what you find out. Worst case I'll install jdk8. |
|
I could not find any configuration options on the javadoc plugin that would allow the build to continue while using JDK11+. The only approach that might work is to use the toolchain plugin. That would help lock the JDK version used for building, but it would still require each maintainer to install JDK8 and generate a toolchains.xml file. I don't think it would be worthwhile at this time. |
|
I'll downgrade to jdk8 and try again. |
|
1.6.0 should be out now ! |
|
Fantastic! I'll follow up with a PR for website and readme changes. |
|
Submitted #214 . |
@tipsy this should make a new release (1.6.0). Nothing as major as I had planned long ago, but it is overdue.