Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

Initial plumbing for version ranges #1057

Closed
wants to merge 6 commits into from
Closed

Initial plumbing for version ranges #1057

wants to merge 6 commits into from

Conversation

davidfowl
Copy link
Member

  • Added RequestedVersion to Library as IVersionSpec
  • Removed Snapshots from SemanticVersion and added them to
    VersionSpec instead.

Things left to implement:

/cc @lodejard @loudej

@davidfowl davidfowl force-pushed the version-specs branch 3 times, most recently from 6240ebd to bf16be2 Compare January 13, 2015 19:13
- Added RequestedVersion to Library as IVersionSpec
- Removed Snapshots from SemanticVersion and added them to
VersionSpec instead.
- When searching through versions, PreferredRequestedVersion should be used.
- Clean up restore from global.json
- Added LibraryRange and SemanticVersionRange
- Changed IsSnapshot to SemanticVersionFloatBehavior to allow floating parts
of the version generically. This allows for node like syntax like ^{version} and
~{version}.
- Changed places that had Library to LibraryRange
-
- Added default LibraryDependency.Type
- Fixed null check in BuildContext
- If a version is specified without floating behavior then only
match if it's an exact version. The trick is to change the UnresolvedDependencyProvider
to return a library with Resolved = false. This allows the unresolved dependency
to be used in the cousin resolution, but if the unresolved dependency is chosen,
it still won't work.
@davidfowl davidfowl closed this Jan 16, 2015
@davidfowl davidfowl deleted the version-specs branch January 19, 2015 07:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant