tazel.net/content, branch content/document-label The site of Tazel, tazel.net. Look up Progmasoft's groups only in Progmasoft's repository 2026-11-06T06:28:12+00:00 Leitwolf11 2026-11-06T06:28:12+00:00 a8d5c015e13bcee918b3140442d7da5e82a71380 The settings of the plugin example listed the Gradle Plugin Portal first and filtered only the Progmasoft repository, so Gradle asked the Portal for com.progmasoft.tazel.plugin before Progmasoft's own repository. The example now makes https://maven.progmasoft.com/tazel exclusive for com.progmasoft.tazel and its subgroups: Gradle resolves those there and nowhere else, and every other plugin from the Portal. The example builds as written: the Gradle plugin and tazel-api resolve and jar writes the plugin JAR with its descriptor. 
The settings of the plugin example listed the Gradle Plugin Portal first
and filtered only the Progmasoft repository, so Gradle asked the Portal for
com.progmasoft.tazel.plugin before Progmasoft's own repository. The
example now makes https://maven.progmasoft.com/tazel exclusive for
com.progmasoft.tazel and its subgroups: Gradle resolves those there and
nowhere else, and every other plugin from the Portal.

The example builds as written: the Gradle plugin and tazel-api resolve
and jar writes the plugin JAR with its descriptor.
Show how a plugin build finds the Gradle plugin of Tazel 0.4.0.3 2026-11-06T05:23:12+00:00 Leitwolf11 2026-11-06T05:23:12+00:00 d17cee854076ddc3ea044e10be66b808af1f247c 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. 
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.
Build the site of Tazel with Nuxt 2026-11-05T02:56:00+00:00 Leitwolf11 2026-11-05T02:56:00+00:00 6f114e3df68d0b20c7e58c5ffb8c46070317008a tazel.net is the site of Tazel itself: a Nuxt 4 site generated to static files, in en-US, de-DE, ru-RU and he-IL, light by default with a dark theme that is kept per browser. - Home: the release and its kind, what Tazel does, the steps from a project file to a program, and a sample. - Docs: Markdown through Nuxt Content, highlighted by Shiki (Kotlin, shell, PowerShell, and Tala through the grammar of the compiler repository), with a tree of the pages on the left, the headings of the page on the right, and the previous and next pages below. Installation, a first project, and releases and support are written in every language; the reference (commands, project file, lockfile, plugins, how Tazel works) is copied from the Documents of Tazel by scripts/sync-docs.mjs, and a language without a page shows the English one with a note. - Every page has its canonical address, hreflang alternates and a sitemap entry; generation fails on a link to a page that does not exist. CI checks the format, the types and the language helpers, generates the site and runs Dependency Review on pull requests. 
tazel.net is the site of Tazel itself: a Nuxt 4 site generated to static
files, in en-US, de-DE, ru-RU and he-IL, light by default with a dark
theme that is kept per browser.

- Home: the release and its kind, what Tazel does, the steps from a
  project file to a program, and a sample.
- Docs: Markdown through Nuxt Content, highlighted by Shiki (Kotlin,
  shell, PowerShell, and Tala through the grammar of the compiler
  repository), with a tree of the pages on the left, the headings of
  the page on the right, and the previous and next pages below.
  Installation, a first project, and releases and support are written
  in every language; the reference (commands, project file, lockfile,
  plugins, how Tazel works) is copied from the Documents of Tazel by
  scripts/sync-docs.mjs, and a language without a page shows the
  English one with a note.
- Every page has its canonical address, hreflang alternates and a
  sitemap entry; generation fails on a link to a page that does not
  exist.

CI checks the format, the types and the language helpers, generates
the site and runs Dependency Review on pull requests.