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

Add support for multiple server credentials in Maven #427

Closed
reckart opened this issue Dec 9, 2022 · 2 comments
Closed

Add support for multiple server credentials in Maven #427

reckart opened this issue Dec 9, 2022 · 2 comments
Assignees
Labels
feature request New feature or request to improve the current logic

Comments

@reckart
Copy link

reckart commented Dec 9, 2022

Description:
Currently, it is possible to generate a settings.xml that contains exactly one server section with GH credentials.
Instead, it should be possible to generate multiple server sections with GH credentials.

Justification:
When a project depends on multiple other projects that each use GitHub packages, then it needs to include a repository declaration for each of these. However, these repository declarations cannot all use the same ID github because the IDs must be unique. So in order to be able to draw in dependencies from multiple GitHub packages repositories, it must be possible to generate multiple server sections, one for each of the GitHub packages repositories.

@reckart reckart added feature request New feature or request to improve the current logic needs triage labels Dec 9, 2022
@marko-zivic-93
Copy link
Contributor

Hello @reckart
Thank you for bringing this up! We will investigate this issue and come back to you as soon as we have some useful information! 😃

@IvanZosimov
Copy link
Contributor

Hi, @reckart 👋 Sorry, but this feature request is a duplicate of #85. I'm going to close your feature request now, meanwhile you can track #85.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request to improve the current logic
Projects
None yet
Development

No branches or pull requests

4 participants