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 SNAPSHOTs. #5

Open
cgruber opened this issue Jan 9, 2019 · 0 comments
Open

Support SNAPSHOTs. #5

cgruber opened this issue Jan 9, 2019 · 0 comments
Assignees
Labels
Type-enhancement New feature or request

Comments

@cgruber
Copy link
Collaborator

cgruber commented Jan 9, 2019

Note - this could be an "at the time of workspace evaluation" resolution, or it could involve pinned versions. Either way, the repository structure file system structure of http://some.repo.root/maven/com/google/dagger/2.20/dagger-2.20.jar doesn't work for snapshots, which are, for the standard "HEAD-SNAPSHOT" version dagger uses, more like: https://oss.sonatype.org/content/repositories/snapshots/com/google/dagger/dagger/HEAD-SNAPSHOT/dagger-HEAD-20190108.194818-169.jar

So this would need to either have pinned versions declared, and then test for the "${version}-${date}.${integer1}-${integer2} version pattern and go into the "${version}-SNAPSHOT" folder to fetch it, or it would need to test for "-SNAPSHOT" and pull the maven-metadata.xml file, grab the snapshot details, and construct the path that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type-enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant