-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the Maven publish #379
Conversation
Hey @vibrantvarun @cwperks can you please review? this should fix the issue that we see with JS maven publish. |
Signed-off-by: Prudhvi Godithi <pgodithi@amazon.com>
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #379 +/- ##
============================================
- Coverage 28.77% 28.69% -0.09%
+ Complexity 97 96 -1
============================================
Files 22 22
Lines 1178 1178
Branches 109 109
============================================
- Hits 339 338 -1
Misses 818 818
- Partials 21 22 +1 |
Hi @prudhvigodithi, thank you for raising this PR! It looks like the I see that this reintroduces |
Hey @cwperks thanks for checking, this PR targets removing all the code added that will hijack the task dependencies, adding task dependencies on the fly in |
@prudhvigodithi Thank you for the explanation. I'm not sure what changed in gradle 8 that made the If we can use other commands in place of a single command to publish all artifacts than that sounds fine to me. |
Testing on my local machine. |
Hey @prudhvigodithi facing below error while testing on my local machine
|
Thanks @vibrantvarun that error does not look like the error related to this PR? (Did not throw in the CI checks as well) @cwperks can you also please test on your local once ? |
|
@prudhvigodithi I do not receive that error on my local machine. @vibrantvarun did you have any issues when checking out Prudvhi's branch that prevented the switching to the branch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Tested on my machine. Thanks @prudhvigodithi
Signed-off-by: Prudhvi Godithi <pgodithi@amazon.com> (cherry picked from commit 946b0ca)
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.7 2.7
# Navigate to the new working tree
cd .worktrees/backport-2.7
# Create a new branch
git switch --create backport/backport-379-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 946b0cafecda71bd5b19220a67a1e61af6081382
# Push it to GitHub
git push --set-upstream origin backport/backport-379-to-2.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.7 Then, create a pull request where the |
Description
Fixes the JS, JS-SPI and JS plugin zip maven publication.
Issues Resolved
#374
#377 (comment)
Testing Output:
For testing purposes I have used
url 'file://Users/pgodithi/.m2/repository'
forSnapshots
RepoFor JS-SPI
For JS
For JS plugin zip
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.