-
Notifications
You must be signed in to change notification settings - Fork 19
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
Allow optional downloading of metadata #4
Comments
These are all files that Maven Servers generated themselves. As a client, you upload your artifacts using Maven's http APIs and the Maven Server is the one who generates checksum and maven-metadata files. The tool will therefor avoid transferring such generated files. Do you have a particular use case where this doesn't apply? |
Been a bit since this issue was opened, but I figured I'd point this out: According to the Apache Maven docs:
It appears that Maven repos aren't supposed to generate these automatically - it just happens that this is something that Nexus does. When copying artefacts from a Nexus server to a Reposilite v3 server, this results in clients being unable to resolve snapshot releases, as mvncloner doesn't upload the metadata files. |
Thanks for the clarification and for pointing out a use case @gdude2002 ! If someone would like to submit a PR that adds a command-line option like |
Hi, great tool.
I've got a use case where I need to completely clone all contents of a repo, including metadata. The checksum files are used for some purpose, and they must also be transferred.
I see these are hardcoded to have exclusion lists at the moment:
https://github.com/netmikey/mvncloner/blob/master/src/main/java/io/github/netmikey/mvncloner/mvncloner/Scraper.java#L45-L49
Would it be possible to make this optional?
I've been able to work around it by replacing the existing lists with nonsense strings that will never match.
The text was updated successfully, but these errors were encountered: