Prepare CQEngine Next 1.0.0 for Maven Central deployment#7
Draft
Prepare CQEngine Next 1.0.0 for Maven Central deployment#7
Conversation
- Update pom.xml version from 1.0.0-SNAPSHOT to 1.0.0 - Update README.md with Maven Central availability and version 1.0.0 - Update CHANGELOG.md with 1.0.0 release information - Add RELEASE.md with comprehensive deployment guide - Verify build success with all required artifacts (main jar, sources, javadoc) Co-authored-by: MSaifAsif <6280554+MSaifAsif@users.noreply.github.com>
- Change maven-javadoc-plugin goal from javadoc-no-fork to jar - Ensures javadoc JAR is properly created during verify phase - Verified all 4 required artifacts are now generated correctly Co-authored-by: MSaifAsif <6280554+MSaifAsif@users.noreply.github.com>
- Create DEPLOYMENT_CHECKLIST.md with quick reference guide - Lists all completed pre-deployment verifications - Provides step-by-step deployment instructions - Includes build commands and verification steps Co-authored-by: MSaifAsif <6280554+MSaifAsif@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Prepare project for initial deployment to Maven Central
Prepare CQEngine Next 1.0.0 for Maven Central deployment
Dec 19, 2025
Owner
|
@copilot Can you also ensure that javadocs and sources are also going to be published ? |
…ment - Remove explicit phase declarations from maven-source-plugin and maven-javadoc-plugin - Let plugins run in their default phases to ensure proper artifact attachment - Verified all artifacts (main, sources, javadoc) are built and installed correctly Co-authored-by: MSaifAsif <6280554+MSaifAsif@users.noreply.github.com>
Contributor
Author
Yes, both javadoc and sources JARs are configured and will be published to Maven Central. I've verified the configuration in commit 5ef7b3b. The build now properly generates and attaches:
All will be deployed to Maven Central when running |
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
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.
Prepare CQEngine Next 1.0.0 for Maven Central Release
✅ All Steps Completed:
🎯 Project Ready for Maven Central Deployment
The project is fully prepared for its first official release to Maven Central. All requirements are satisfied:
Maven Central Compliance:
Documentation:
🚀 Next Steps (Manual - Requires OSSRH Account & GPG Key):
Deploy to Maven Central:
cd code mvn clean deploy -Prelease-sign-artifacts -DperformRelease=trueRelease from OSSRH Staging:
Create GitHub Release:
v1.0.0When deployed, Maven Central will receive:
See RELEASE.md for detailed instructions and troubleshooting.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.