-
Notifications
You must be signed in to change notification settings - Fork 60.6k
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
Issue 1669: Update GitHub Maven docs Super POM and context #1670
Conversation
The GitHub Maven configuration overrides default behaviors of the Maven Super POM on central releases. It additionally makes notes on configuring user settings out of context of consuming projects of packages.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Comments are stripped from code fences in github markdown for XML
Attempting to retain comments in documentation.
GitHub Markdown strips comments from code fences. Attempting to retain comments with explicit HTML element.
GitHub Maven Packages may require multiple repositories where many different packages are used or consumed. This is a limitation of the group/organization package resolution.
Thanks so much for opening a PR! I'll get this triaged for review ⚡ |
This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit. |
Thanks for your patience! Our small team is working our way through reviewing all of the amazing contributions ✨ |
This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit. |
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.
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.
@janiceilene @ayiem @evic0525 sorry for the late sync/merge/push. resolved conflicts. |
This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit. |
This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit. |
@timothystone I hope you don't mind. I've pushed a few changes/simplifications to your PR branch. I thought it might accelerate getting this PR merged. 🤞🏻 |
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
data/reusables/package_registry/apache-maven-snapshot-versions-supported.md
Outdated
Show resolved
Hide resolved
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.
Thank you everyone for your contributions here. I just added a product variable. This looks good from a docs team perspective. ⚡
@jmarlena thanks for the edit. apologies for being late to the discussion! I had lost track of this PR amid some work happening in my day job. |
Why:
The GitHub Maven configuration overrides default behaviors of the Maven Super POM on central releases. It additionally makes notes on configuring user settings out of context of consuming projects of packages.
See #1669
What's being changed:
Documentation on Maven Configuration for GitHub Packages.
Check off the following: