Skip to content
This repository has been archived by the owner on May 12, 2018. It is now read-only.

Fix false reporting of (plain) vsn strings #173

Merged
merged 1 commit into from Dec 3, 2013
Merged

Fix false reporting of (plain) vsn strings #173

merged 1 commit into from Dec 3, 2013

Conversation

ghost
Copy link

@ghost ghost commented Nov 24, 2013

rebar used to mistakenly report plain version strings like
{vsn, "1.0.0"} as follows:
DEBUG: vcs_vsn: Unknown VCS atom in vsn field: "1.0.0"

Properly detect unknown/unsupported version terms and abort
if we encounter one.

While at it, rename a variable in vcs_vsn/3 to be non-misleading.

rebar used to mistakenly report plain version strings like
{vsn, "1.0.0"} as follows:
DEBUG: vcs_vsn: Unknown VCS atom in vsn field: "1.0.0"

Properly detect unknown/unsupported version terms and abort
if we encounter one.

While at it, rename a variable in vcs_vsn/3 to be non-misleading.
@jaredmorrow
Copy link
Contributor

+1, thanks

jaredmorrow added a commit that referenced this pull request Dec 3, 2013
Fix false reporting of (plain) vsn strings
@jaredmorrow jaredmorrow merged commit dac4f92 into rebar:master Dec 3, 2013
@ghost ghost deleted the unknown-vsn branch December 3, 2013 21:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
1 participant