fix: point mainClass at the renamed package - #151
Merged
Conversation
The package rename from net.theevilreaper.* to net.onelitefeather.* never reached application.mainClass, so Micronaut wrote a stale Main-Class into application.jar. The container entrypoint runs `java -jar /home/app/application.jar`, which made every pod die with ClassNotFoundException: net.theevilreaper.vulpes.generator.VulpesGenerator. Verified via `./gradlew buildLayers`: the manifest now reads Main-Class: net.onelitefeather.vulpes.generator.VulpesGenerator.
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.
Problem
Jeder Pod stirbt beim Start:
Ursache
Die Package-Umbenennung
net.theevilreaper.*→net.onelitefeather.*hatapplication.mainClassinbuild.gradle.ktsnie erreicht. Micronaut schreibt diesen Wert alsMain-Classinapplication.jar, und der generierte Entrypoint istjava -jar /home/app/application.jar— also lief der Container gegen einen Klassennamen, den es seit der Umbenennung nicht mehr gibt.Fix
Einzeiler in
build.gradle.kts.Verifikation
./gradlew buildLayersgebaut und das Manifest geprüft:Main-Class: net.onelitefeather.vulpes.generator.VulpesGeneratornet/onelitefeather/vulpes/generator/VulpesGenerator.classliegt im JarEs war die letzte aktive
theevilreaper-Referenz im Repo (die verbleibende insettings.gradle.kts:50ist auskommentiert).