master Changelog gradle-3.0.0-beta ================= - gradle-3.0.0-beta.23 Bump Git Version to 0.7.0 - gradle-3.0.0-beta.22 Fix subprojects failing to publish changelogs Temporarily disabled changelog gen for this build so that it will work. - gradle-3.0.0-beta.21 Update workflows to account for project restructuring - gradle-3.0.0-beta.20 Split off GitVersion and Changelog plugins into two separate jars The Changelog plugin now exists in `:gitversion-gradle:changelog-gradle`. This was done because the GitVersion plugin can be applied onto any type (including settings) while Changelog can only be applied onto projects. If a consumer were to apply the GV plugin in `settings.gradle` and then later apply the Changelog plugin in `build.gradle`, it could cause an error where the plugin could already be on the classpath with an unknown version. The only code shared by these two projects is a single class `GitVersionTools` that has the definition for the tool to download and invoke. This has been split off into `:gitversion-gradle:common` and is shadowed by both projects. - gradle-3.0.0-beta.19 Fix actions workflow using wrong Gradle project name - gradle-3.0.0-beta.18 Migrate buildscript to GU3, dogfood GV3 on root project - gradle-3.0.0-beta.17 Bundle shared base with GV3 - gradle-3.0.0-beta.16 Fix task dependencies for copyChangelog in subprojects - gradle-3.0.0-beta.15 Allow plugin to be applied on settings.gradle - gradle-3.0.0-beta.14 Fix CopyChangelog failing to execute Missed an `@Internal` annotation - gradle-3.0.0-beta.13 More cleanup, (try to) get shadow jar working again - gradle-3.0.0-beta.12 Account for recent change in GradleUtils https://github.com/MinecraftForge/GradleUtils/commit/7b5fda38c36d22e2300af7babeb190d6dc257217 - gradle-3.0.0-beta.11 Add --output flag to output info to file instead of stdout - gradle-3.0.0-beta.10 Fix implementation issue with GenerateChangelog - gradle-3.0.0-beta.9 Fix configuration cache issues This one's a bit weird. Gradle stores *the effects* of providers in order to execute them without needing to configure the project. However, in order to get the execution path for the Java launcher, we need access to the JavaToolchainService, which is usually injected at configuration. The problem is that this service is not available if we are skipping configuration (i.e. configuration cache). The solution is to not worry about setting a Java launcher executable path. This plugin requires Gradle 9 which itself requires Java 17. Git Version is built using Java 17. We can count on the daemon JVM being at least version 17 and don't need to worry about setting the Java launcher in the JavaExec spec ourselves. - gradle-3.0.0-beta.8 Fix Git Version value source eagerly resolving toolchain - gradle-3.0.0-beta.7 Account for an issue with method refernces in Groovy Method refernces (::) and pointers (.&) to private methods when used as a closure cause illegal access issues. - gradle-3.0.0-beta.6 Fixed some silly mistakes that caused resolution errors - gradle-3.0.0-beta.5 Update Foojar Resolver Convention to fix builds 0.10.0 is incompatible with Gradle 9 due to a refernce in Gradle 8 that no longer exists. - gradle-3.0.0-beta.4 Fix workflow paths, increment build numbers - gradle-3.0.0-beta.3 Comment stubs to get the plugin building - gradle-3.0.0-beta.2 Fix use of local libraries, use Git Version 0.6.1 - gradle-3.0.0-beta.1 Temporarily disable publishing to plugin portal Actions workflow doesn't have the secret keys for it yet, but I need to start testing now. - gradle-3.0.0-beta.0 0.6 - Dedicated Gradle plugin, Changelog from CLI, API restructuring (#2)