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

Support proxying repositories in Github and Bitbucket #2

Open
fjmilens3 opened this issue Feb 23, 2018 · 2 comments
Open

Support proxying repositories in Github and Bitbucket #2

fjmilens3 opened this issue Feb 23, 2018 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@fjmilens3
Copy link
Contributor

The proof-of-concept implementation assumes that all dist urls point to a Github repository. Packagist also supports Bitbucket as a first class citizen via webhooks (https://packagist.org/about) so we should likely support that as a minimum before calling this "done."

Supporting Bitbucket would also match existing user expectations from similar formats (e.g. for Bower, which has a similar index mechanism that also points to Git repositories, we consider Github and Bitbucket support to meet our internal "definition of done" for that format).

If you're a Sonatype employee, consult the Bower implementation for ideas on how to do this. If you're not but you want to work on this, feel free to ping us for ideas on where to get started on this issue.

@fjmilens3
Copy link
Contributor Author

Note that this may work out of the box since we don't have a hardcoded requirement, but we haven't tested it against anything else.

We should verify that it works for both, particularly since we do assume that we're going to be obtaining a zip file from the upstream repo.

@fjmilens3 fjmilens3 added enhancement New feature or request good first issue Good for newcomers labels Jun 18, 2018
@fjmilens3
Copy link
Contributor Author

This would be worth investigating once the refactoring for non-Packagist repositories is merged.

stklcode added a commit to stklcode/nexus-repository-composer that referenced this issue Apr 20, 2024
# Das ist die erste Commit-Beschreibung:

update explicit Maven plugin versions

# Die Commit-Beschreibung sonatype-nexus-community#2 wird ausgelassen:

# plugin++
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant