Resolver Tests are locked to DEFAULT_REPOSITORY

sam / doubleshot

Build and Dependency Management for mixed Java/Ruby projects.

MIT License

19 stars 22 forks source link

Resolver Tests are locked to DEFAULT_REPOSITORY #60

Closed sam closed 12 years ago

sam commented 12 years ago

JarResolver Tests are sporadically failing because we're hard-coding Central for the repository in the test.

We should use the current configuration's repositories in the tests to avoid this.

This applies to both Gems and JARs.

sam commented 12 years ago

Doesn't actually apply to Gems since we're we're stubbing those. Except for the gem_source_spec, in which case we need a live Rubygems server and rubygems.org is as good as any then for an external dependency.