chore: add group Gradle property; add maven-publish plugin #1274
Conversation
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
Signed-off-by: Valeriy Svydenko <vsvydenk@redhat.com>
|
@amvanbaren thank you for merging my previous PR! |
|
@svor Where does it publish to? When I run |
@amvanbaren |
|
@amvanbaren Do you have any concerns about these changes? |
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.
This pull request introduces changes to the Gradle build configuration to enable Maven publishing and support Red Hat's Project Manipulation Extension (PME).
Gradle Build Configuration Enhancements:
maven-publishplugin to thepluginsblock to enable Maven publishing.publishingblock to configure Maven publications, including publishing thebootJarartifact and a script (scripts/run-server.sh).Gradle Properties Update:
groupproperty (org.eclipse.openvsx) to support Red Hat's Project Manipulation Extension (PME) work.How to test
These changes should not impact the existing OpenVSX server build process.
To verify, you can run the following command: