Fix Maven support - #21
Open
chums122 wants to merge 6 commits into
Open
Conversation
* Switch run configuration defaults to be Maven-aware (package for Maven projects, shadowJar for Gradle).
* Update build task UI to show Maven goals for Maven projects and include clean package.
* Add one-time startup migration prompt for existing Maven projects using Gradle-only tasks, with actions:
* Migrate to package
* Keep current task
* Improve build execution:
* Support multi-token tasks/goals (e.g. clean package)
* Normalize Gradle-only task names to package when executing Maven.
* Improve plugin metadata detection by parsing pom.xml (groupId/artifactId/name/version) and returning Maven jar/task defaults.
* Remove Maven template auto-copy (maven-resources-plugin copy-to-mods) so deployment is handled only by the IntelliJ plugin.
-Added Maven support in hot reload build path - Better Maven detection in startup setup - Updated outdated Gradle-only message - Cleaned plugin.xml text for encoding safety
chums122
changed the title
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.
Summary
This PR completes Maven support across run/build/deploy paths and removes Maven/Gradle mismatches that caused build lifecycle failures.
What changed
Maven-aware run config defaults
packageshadowJarBuild task UI now adapts by build system
packageclean packageinstallverifycleanshadowJarbuildjarassembleOne-time migration prompt for existing Maven configs
build,shadowJar,jar,assemble), the plugin shows a notification with:Migrate to packageKeep current taskMaven execution hardening in run state
clean package).packagewhen executing with Maven.Hot Reload now supports Maven too
HotReloadPluginActionbuild step now supports:build/libsandtarget.Improved Maven project detection during startup setup
isHytaleProject()now also checks pom.xml for Hytale dependency markers:com.hypixel.hytale<artifactId>Server</artifactId>Better reconfigure messaging
Remove duplicate Maven deploy behavior
maven-resources-plugincopy-to-modsexecution from Maven template pom.xml.Text encoding cleanup in plugin metadata
|,->) to avoid mojibake.Why
Maven projects were failing due to Gradle-centric task defaults and options, and hot reload was Gradle-only. This PR aligns defaults, UI, startup behavior, and execution paths with Maven semantics.
Validation
gradlew.bat -q compileKotlin passes after changes.