Fix Maven build configuration issues and remove development artifacts #270
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.
This PR resolves several Maven build configuration issues that were causing warnings during compilation and potentially affecting build stability.
Issues Fixed
1. Duplicate Dependencies
shared/pom.xml(lines 161-165 and 179-183 both declared version 20231013)cli/pom.xml(kept 4.5.14, removed 4.5.13)2. Deprecated Version Declaration
LATESTversion to specific version0.18.2inshared/pom.xml3. Development Artifact Cleanup
Before
Maven builds showed multiple warnings:
After
Clean Maven builds with no dependency-related warnings. All existing tests continue to pass (314 tests in CLI module, 51 tests in shared module).
Impact
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
www.jdeploy.comjava -jar /home/REDACTED/work/jdeploy/jdeploy/tests/../cli/target/jdeploy-cli-1.0-SNAPSHOT.jar clean package(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.