Migrate build tooling from Gradle to Maven#1
Open
hermanngeorge15 wants to merge 1 commit into
Open
Conversation
Gradle is unusable in the target corporate environment, so all 16 lesson projects (session-01, start + finish) now build with Maven instead. - Add pom.xml per project: Kotlin 2.0.21, kotlin-maven-plugin with jvmTarget=21 (matches former jvmToolchain(21)), sourceDirectory=src/main/kotlin, exec-maven-plugin for `mvn compile exec:java` - Remove build.gradle.kts, settings.gradle.kts, gradlew, gradlew.bat, and gradle/wrapper/ (96 files) - Update SETUP.md, README.md, lesson-01/README.md: Gradle -> Maven - .gitignore: build/ + .gradle/ -> target/ (+ .kotlin/) IntelliJ green-button workflow is preserved (bundled Maven, no CLI needed), which also avoids the corporate Gradle-download issue. Validated on JDK 24: all 16 projects compile clean; lesson-08-final runs with correct output (no more class-version-68 error). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Gradle is unusable in the target corporate environment (download/proxy restrictions), so the workshop must build with Maven to actually run on attendees' machines.
What changed
pom.xmlto all 16 lesson projects (session-01,start+finish): Kotlin 2.0.21,kotlin-maven-pluginwithjvmTarget=21(matches the formerjvmToolchain(21)),sourceDirectory=src/main/kotlin(no file moves),exec-maven-pluginformvn compile exec:java.build.gradle.kts,settings.gradle.kts,gradlew,gradlew.bat,gradle/wrapper/.SETUP.md,README.md,lesson-01/README.mdupdated Gradle → Maven..gitignore:build/+.gradle/→target/(+.kotlin/).Student UX preserved
IntelliJ green-▶-on-
main()works identically for Maven, using IntelliJ's bundled Maven — no CLI install, which also avoids the corporate Gradle-download issue. Nomvnwadded for the same reason.Validation
Tested on JDK 24 (the env that triggered the prior Gradle class-version-68 errors):
lesson-08-final/finishcompiles and runs with correct Expense Report output🤖 Generated with Claude Code