Skip to content

Releases: gretty-gradle-plugin/gretty

3.1.0

11 Nov 17:25
79ab4f9
Compare
Choose a tag to compare

What's Changed

  • Isolate Classpaths of CLI Runner and Servlet Container by @f4lco in #270

  • Compile on JDK 11 and add Jetty 10 by @f4lco in #268

  • Support of the Jetty 10 servlet container

  • Reworked classloader concept to stop leakage of Gretty's dependencies onto the webapp classpath

  • Dropped support for Logback entirely, because of the slf4j 1.x / 2.x ecosystem split

Full Changelog: v3.0.9...v3.1.0

3.0.9

15 Sep 12:25
229ccc8
Compare
Choose a tag to compare
  • Replace internal Gradle API usage with public API #265
    Thank you, @octylFractal, for making Gretty better.

4.0.3

24 Aug 14:01
212f07c
Compare
Choose a tag to compare
  • Replace internal Gradle API usage with public API #263
    Thank you, @octylFractal, for making Gretty better.
  • Upgraded default versions of Tomcat to 10.0.22, and Jetty to 11.0.11

4.0.2

02 Jun 10:48
9474421
Compare
Choose a tag to compare
  • Use Tomcat 10.0.21
  • Use Jetty 11.0.9
  • Use Gradle 7.4.2 for testing Gretty
  • Added exclusion patterns for commons-cli and commons-io classes to FilteringClassLoader #258
    Adding the patterns fixes a bug which gave preference to the commons-cli and commons-io versions
    that Gretty uses, rather than using the JARs bundled with the webapp (which is the correct behavior).
  • Upgrade to Logback 1.3.0-alpha14
  • Remove Groovy-based logging configuration in response to Log4Shell #249

3.0.8

01 Jun 19:30
5cdec58
Compare
Choose a tag to compare

Thanks @boris-petrov for patch #258, that updated exclusion patterns for FilteringClassLoader, which causes Gretty to correctly use the commons-io and commons-cli JARs from the webapp classpath rather than defaulting on the versions shipped with Gretty.

4.0.1

25 Feb 13:53
75e1ee5
Compare
Choose a tag to compare
  • Fix inability to build a product due to missing Groovy dependencies (#238).

  • Version upgrades to mitigate some CVEs (#252). Thanks to @dutta1kartik3.

3.0.7

28 Oct 06:17
1bfe83d
Compare
Choose a tag to compare
  • Fix inability to build a product due to missing Groovy dependencies (#238)

4.0.0

01 Sep 10:48
0a90428
Compare
Choose a tag to compare
  • Gretty requires JDK11+.

  • Gretty supports only Tomcat 10 and Jetty 11 (Jakarta versions of the containers). All thanks goes to @f4lco.

3.0.6

27 Jul 08:32
482794f
Compare
Choose a tag to compare
  • JDK 16 support

3.0.5

28 Jun 10:55
v3.0.5
d07ce7e
Compare
Choose a tag to compare

Please note that Gretty 3.0.5 is the first one not using JCenter but rather Maven Central. Be sure
to change your jcenter() to mavenCentral() in your Gradle files.

  • Changes in this version:

  • Added some release details for Maven Central.

  • Added uploadArchives for upload to Maven Central.

  • Restored simple GPG signing in prep for replacement of Bintray with Maven Central.

  • Build with Gradle 6.x in Jitpack

  • Use a fixed Gecko driver version

  • Use Gradle 6.9 for the "global" build

  • Fix the gradle clean task

  • Update some packages

  • Gradle defines version as an object so we need to make sure we are doing explicit to String conversion

  • Revert "Purge identical builds by removing 'pull_request' trigger from GH actions"

  • Replace deprecated JavaExec.main usage with JavaExec.mainClass property

  • Merge pull request #218 from brandonramirez/loopback_address_bind

  • Update Gradle wrapper to 7.0-rc-2

  • Remove Gradle wrapper task definitions

  • Add Java 16 and build only against currently supported versions of Java

  • Update actions/setup-java

  • Purge identical builds by removing 'pull_request' trigger from GH actions

  • Run tests on JUnit 5 on Gradle 7

  • Upgrade dependencies in Gradle 7 build

  • Replace jcenter repository with Maven Central

  • Rely on Groovy version shipped with Gradle

  • Add Gradle 7 build job

  • Explicitly bind to loopback address rather than local address to fix a BindException.

  • Use the springBoot option when it is not null (#213)

  • Avoid calling afterEvaluate on already evaluated project

  • Remove unused import

  • Improve the code structure

  • Improve the dependency resolving logic

  • Update Gradle's version in CI

  • [skip ci] Remove mentions of Tomcat 10 in the changes.md file too

  • Remove publishing to Bintray on push

  • Fixed 'multiple plugins are using the same ID' error in publishPlugins. (#211)