Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/scripts
diff options
context:
space:
mode:
authorLeitwolf112026-11-06 08:23:12 +0300
committerLeitwolf112026-11-06 08:23:12 +0300
commitd17cee854076ddc3ea044e10be66b808af1f247c (patch)
tree49df0937a7005a8f2439c7c516b76df5c52c9492 /scripts
parent3da7af66f343e532a9ea2aa7236152bf2225499b (diff)
downloadtazel.net-d17cee854076ddc3ea044e10be66b808af1f247c.tar.gz
Show how a plugin build finds the Gradle plugin of Tazel 0.4.0.3
The Building a plugin section asked for com.progmasoft.tazel.plugin 0.4.0 from the Gradle Plugin Portal alone. The Portal does not serve it yet, and the released version is 0.4.0.3. The example now has the settings.gradle.kts that adds https://maven.progmasoft.com/tazel for the group com.progmasoft.tazel, uses version 0.4.0.3, and adds Maven Central, without which Kotlin's standard library does not resolve. The example was built as written: the Gradle plugin and tazel-api 0.4.0.3 resolve and gradlew jar writes the plugin JAR with its descriptor. Progmasoft/tazel carries the same change in Documents/PLUGINS.md for the next release, so the next sync keeps it.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions