Bump jteVersion from 2.0.2 to 2.3.0

[dependabot]

Bumps jteVersion from 2.0.2 to 2.3.0.
Updates gg.jte:jte from 2.0.2 to 2.3.0

Release notes

Sourced from gg.jte:jte's releases.

2.3.0

This release bumps Kotlin to 1.8 and Gradle to 8.0 (see #177). This affects only users who use .kte template and/or use the jte Gradle Plugin for precompiling templates.

In case your app is still not on Kotlin 1.8 or Gradle 8.0, it is recommended to stay on jte < 2.3.0 until you are ready to upgrade.

2.2.6

This release improves the jte-spring-boot-starter:

• #195 add dedicated starter for spring boot 3 (thanks @​atomfrede)
• #190 Fix ReactiveJteViewResolver (thanks @​russ-p)

The jte-spring-boot-starter no longer exists. If you're still on spring boot 2, you can continue using jte-spring-boot-starter-2. If you're already on spring boot 3, you can now use jte-spring-boot-starter-3.

2.2.4

• #185 Rendering Enums calls name(), instead of toString()
• #186 Add hot reload support to ResourceCodeResolver
• #189 properly reset escaping context after attribute value

2.2.3

• #182 fix interpolation in intercepted attributes

2.2.2

jte-kotlin

• Revert to Kotlin 1.6.21 until Gradle issues are solved
• #179 suppress warnings in generated Kotlin templates
• #179 suppress Linter in generated Kotlin templates

2.2.1

jte

• #176 null string passed to $unsafe{} behaves the same as if passed to ${}

jte-kotlin

• #177 bump kotlin version to 1.7.20
• #161 unsafe can only be used for rendering strings, was missing in jte-kotlin

2.2.0

jte

• #174 do not output semicolon for !{} expressions in the Java code generator, to be in line with the documentation and the IntelliJ plugin (minor, but possibly breaking change)
• Removed StringOutputPool, as it was a rather arbitrary and minimal class, easily created if needed and also won't work well together with Loom's upcoming virtual threads
• Minor hot reload synchronization improvement

jte-watcher

• Bump io.methvin.directory-watcher to 0.16.1

jte-kotlin

• Bump kotlin version to 1.7.10
• Remove special handling of \f escape sequence that is not supported in Kotlin

2.1.2

• #163 support for Kotlin value classes
• #166 fix for using JS string interpolation inside @raw in template content

... (truncated)

Commits

• 4a1333d Bump version to 2.3.0
• 132982b Update SECURITY.md
• 03041bd Fix jvm target compatibility error
• 2d9687e Delete ignored files
• cdb495f Build gradle tests projects with gradle 8.0.1
• 2ef1bf9 Build gradle plugin with gradle 8.0.1
• 6757c34 Bump kotlin version to 1.8.10
• 2ab5fde #199 add javadoc for TemplateEngine configuration methods, that are only effe...
• 17b8612 Fix javadoc warnings
• 595d412 Add test for trimControlStructures with ContentType#Plain
• Additional commits viewable in compare view

Updates gg.jte:jte-kotlin from 2.0.2 to 2.3.0

Release notes

Sourced from gg.jte:jte-kotlin's releases.

2.3.0

This release bumps Kotlin to 1.8 and Gradle to 8.0 (see #177). This affects only users who use .kte template and/or use the jte Gradle Plugin for precompiling templates.

In case your app is still not on Kotlin 1.8 or Gradle 8.0, it is recommended to stay on jte < 2.3.0 until you are ready to upgrade.

2.2.6

This release improves the jte-spring-boot-starter:

• #195 add dedicated starter for spring boot 3 (thanks @​atomfrede)
• #190 Fix ReactiveJteViewResolver (thanks @​russ-p)

The jte-spring-boot-starter no longer exists. If you're still on spring boot 2, you can continue using jte-spring-boot-starter-2. If you're already on spring boot 3, you can now use jte-spring-boot-starter-3.

2.2.4

• #185 Rendering Enums calls name(), instead of toString()
• #186 Add hot reload support to ResourceCodeResolver
• #189 properly reset escaping context after attribute value

2.2.3

• #182 fix interpolation in intercepted attributes

2.2.2

jte-kotlin

• Revert to Kotlin 1.6.21 until Gradle issues are solved
• #179 suppress warnings in generated Kotlin templates
• #179 suppress Linter in generated Kotlin templates

2.2.1

jte

• #176 null string passed to $unsafe{} behaves the same as if passed to ${}

jte-kotlin

• #177 bump kotlin version to 1.7.20
• #161 unsafe can only be used for rendering strings, was missing in jte-kotlin

2.2.0

jte

• #174 do not output semicolon for !{} expressions in the Java code generator, to be in line with the documentation and the IntelliJ plugin (minor, but possibly breaking change)
• Removed StringOutputPool, as it was a rather arbitrary and minimal class, easily created if needed and also won't work well together with Loom's upcoming virtual threads
• Minor hot reload synchronization improvement

jte-watcher

• Bump io.methvin.directory-watcher to 0.16.1

jte-kotlin

• Bump kotlin version to 1.7.10
• Remove special handling of \f escape sequence that is not supported in Kotlin

2.1.2

• #163 support for Kotlin value classes
• #166 fix for using JS string interpolation inside @raw in template content

... (truncated)

Commits

• 4a1333d Bump version to 2.3.0
• 132982b Update SECURITY.md
• 03041bd Fix jvm target compatibility error
• 2d9687e Delete ignored files
• cdb495f Build gradle tests projects with gradle 8.0.1
• 2ef1bf9 Build gradle plugin with gradle 8.0.1
• 6757c34 Bump kotlin version to 1.8.10
• 2ab5fde #199 add javadoc for TemplateEngine configuration methods, that are only effe...
• 17b8612 Fix javadoc warnings
• 595d412 Add test for trimControlStructures with ContentType#Plain
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)