<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kotlin on The TARDIS Server Project</title><link>https://tardisgallifrey.codeberg.page/tags/kotlin/</link><description>Recent content in Kotlin on The TARDIS Server Project</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Sep 2026 12:11:58 -0500</lastBuildDate><atom:link href="https://tardisgallifrey.codeberg.page/tags/kotlin/index.xml" rel="self" type="application/rss+xml"/><item><title>An overview of Gradle's build.gradle.kts</title><link>https://tardisgallifrey.codeberg.page/posts/gradlelesson2/</link><pubDate>Fri, 11 Sep 2026 12:11:58 -0500</pubDate><guid>https://tardisgallifrey.codeberg.page/posts/gradlelesson2/</guid><description>&lt;h2 id="background-and-beginning"&gt;Background and beginning&lt;/h2&gt;
&lt;p&gt;If you read my previous post, you know that I recently spent a good deal of time debugging a Java build of a program. Not a bug in the Java code, but a bug in gradle, my build environment. Specifically, in my gradle build file: &lt;code&gt;build.gradle.kts&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;After going through that problem, I spent time, finally, not pursuing more programming, but learning how gradle&amp;rsquo;s build operated instead. So, this is a summary of that learning. Sorry, it&amp;rsquo;s going to be a bit long. But, first, I need to take a minute to go over background things so that we are all on the same page. If you read my post about writing and compiling a &lt;em&gt;Hello World!&lt;/em&gt; program in &lt;a href="https://www.tardisgallifrey.com/posts/helloworld"&gt;C and in Java&lt;/a&gt; , you will know what a basic Java program looks like. You will also see that, in theory, you can compile a Java class with &lt;code&gt;javac MyMain.java&lt;/code&gt; into a program.&lt;/p&gt;</description></item></channel></rss>