Skip to content
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

Migrate from maven-artifact-transfer to direct use of Resolver API #118

Merged
merged 5 commits into from
Oct 28, 2024
Merged

Migrate from maven-artifact-transfer to direct use of Resolver API #118

merged 5 commits into from
Oct 28, 2024

Conversation

pyatizbyantsevia
Copy link
Contributor

@pyatizbyantsevia pyatizbyantsevia commented Oct 22, 2024

Fixes #64

Testing done

I tested the plugin in action by running a simple project that reflects how it works: https://github.com/pyatizbyantsevia/jellydoc-maven-plugin-64

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

Other

I'm not sure if using RepositoryUtils methods is a good idea. The description of this class contains the following comment:
Warning: This is an internal utility class that is only public for technical reasons, it is not part of the public API. In particular, this class can be changed or deleted without prior notice.

@pyatizbyantsevia
Copy link
Contributor Author

@basil, please take a look

It would be great to close this as part of Hacktoberfest

@timja timja requested a review from a team October 28, 2024 09:10
@basil basil added internal and removed developer labels Oct 28, 2024
@basil basil changed the title Migrate from maven-artifact-transfer to direct use of Resolver API Migrate from maven-artifact-transfer to direct use of Resolver API Oct 28, 2024
Copy link
Member

@basil basil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

@basil basil merged commit 3b95d6d into jenkinsci:master Oct 28, 2024
0 of 2 checks passed
basil added a commit to jenkinsci/stapler-maven-plugin that referenced this pull request Oct 28, 2024
basil added a commit to jenkinsci/stapler-maven-plugin that referenced this pull request Oct 28, 2024
…ed2 to 195.v4662dd79fdb_d (#124)

* Bump io.jenkins.tools.maven:jellydoc-maven-plugin

Bumps [io.jenkins.tools.maven:jellydoc-maven-plugin](https://github.com/jenkinsci/jellydoc-maven-plugin) from 190.ve454d5e0ced2 to 195.v4662dd79fdb_d.
- [Release notes](https://github.com/jenkinsci/jellydoc-maven-plugin/releases)
- [Commits](https://github.com/jenkinsci/jellydoc-maven-plugin/commits)

---
updated-dependencies:
- dependency-name: io.jenkins.tools.maven:jellydoc-maven-plugin
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>

* Adapt to jenkinsci/jellydoc-maven-plugin#118

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Basil Crow <[email protected]>
@basil
Copy link
Member

basil commented Oct 28, 2024

@pyatizbyantsevia It's superfluous to say that we're grateful for you cleaning up this old Maven plugin. If you're interested in another ticket like this, jenkinsci/maven-hpi-plugin#511 is still open. If not, then thanks again for this contribution!

@pyatizbyantsevia
Copy link
Contributor Author

I want to express my gratitude to everyone involved! It was an interesting experience =)

@pyatizbyantsevia pyatizbyantsevia deleted the resolver-api-usage branch October 29, 2024 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate from maven-artifact-transfer to direct use of Resolver API
4 participants