summaryrefslogtreecommitdiff
path: root/src/rebar_git_resource.erl
Commit message (Collapse)AuthorAgeFilesLines
* Unicode support in all the placesFred Hebert2017-08-061-24/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is done through 3 main change groups: - replacing `~s` by `~ts` in format strings, so that strings that contain unicode are properly printed rather than crashing - adding the `unicode` argument to all function of the `re` module to ensure transformations on strings containing unicode data are valid instead of crashing (see issue #1302) - replacing `ec_cnv:to_binary/1` and `ec_cnv:to_list/1` with matching functions in `rebar_utils`. The last point has been done, rather than modifying and updating erlware commons, because binary and list conversions can be a contentious subject. For example, if what is being handled is actually bytes from a given binary stream, then forcing a byte-oriented interpretation of the data can corrupt it. As such, it does not appear safe to modify erlware commons' conversion functions since it may not be safe for all its users. Instead, rebar3 reimplements a subset of them (only converting atoms and chardata, ignoring numbers) with the explicit purpose of handling unicode string data. Tests were left as unchanged as possible. This may impact the ability to run rebar3's own suites in a unicode path, but respects a principle of least change for such a large patch.
* Fix git SHAs comparison for update.Alin Popa2017-03-121-9/+7
| | | | | | | 86e883b8d8d1d16487e245fff02eba8c83da2cdd always returns the full length SHA, therefore when using a dependency having the short SHA, it'll always consider that the SHAs are different, hence it'll alway return true for .
* Use different git commands for different git versionsBjörn-Egil Dahlberg2016-12-071-13/+59
| | | | | | | | | | The option --single-branch was introduced in git version 1.7.10 and thus rebar3 cannot fetch git dependencies on systems where earlier git versions are install. This commit will select other git clone commands if an earlier git version is detected. If the git version cannot be determined rebar3 falls back on the previous behavior and uses --single-branch.
* Fixes for windows environment: 1) copy empty directories when cloning (since ↵Steve Strong2016-06-281-1/+1
| | | | git occasionally has a refs directory with no files in it - if the directory is not present, then git does not believe it is a git repo) and 2) change order of git rev-parse arguments to match git docs
* Debug log updateStuart Thackray2016-05-271-1/+1
|
* #1185 fix windows git working directoryPost hawk2016-05-181-2/+9
| | | fix issue #1185 git working directory issues due to command line options in Windows
* Fixed git version bugYakov2016-04-041-1/+1
| | | | | | | | | | | | | | | | | I've tried to compile project with git in .app.src vsn Project was tagged as 1.0.0, but resulting .app vsn becomes 1.0.0+build.6.reff0aec24 ```git lg * f0aec24 - (80 минут назад) Fixed ct — Kozlov Yakov (HEAD -> master, tag: 1.0.0, origin/master) ... 5 commits before ``` ``` $ git log --oneline --no-walk --tags --decorate f0aec24 (HEAD -> master, tag: 1.0.0, origin/master) Fixed ct ``` I've found that `HEAD -> master` doest match pattern in [rebar_git_resource](https://github.com/erlang/rebar3/blob/master/src/rebar_git_resource.erl#L204)
* only need to compare ref and not ref+url in git resourceTristan Sloughter2016-01-081-2/+2
|
* if not in a git repo but have 'git' as vsn, fallback to 0.0.0Tristan Sloughter2015-10-041-23/+30
|
* Improve semantic versioning from git between tagsZachary Hueras2015-09-211-1/+7
| | | | | | | | | | | | | | In the scenario we that we have selected a commit that is between two tags, we should base the version on the most recent tag we can see in the revision history, but we should not treat this as the tag version. `git describe --tags --abbrev=0` finds the most recent tag visible in the revision history from the current HEAD. Return this as the version string and undefined as the tag to trigger ref counting.
* Only match current HEAD tag in git semverZachary Hueras2015-09-211-1/+1
| | | | | | | | | In the scenario that someone had cloned an entire repository and then checked out an older version tag, the semantic versioning would detect the newest tag, not the checked out tag. Look for the HEAD string prior to tag: to indicate the currently selected tag.
* make v prefix in git tag version optionalTristan Sloughter2015-09-191-1/+1
|
* Revert "Improved git versioning"Tristan Sloughter2015-09-191-8/+2
|
* Improve semantic versioning from git between tagsZachary Hueras2015-09-161-1/+7
| | | | | | | | | | | | | In the scenario we that we have selected a commit that is between two tags, we should base the version on the most recent tag we can see in the revision history, but we should not treat this as the tag version. `git describe --tags` finds the most recent tag visible in the revision history from the current HEAD. Return this as the version string and undefined as the tag to trigger ref counting.
* Only match current HEAD tag in git semverZachary Hueras2015-09-161-1/+1
| | | | | | | | | In the scenario that someone had cloned an entire repository and then checked out an older version tag, the semantic versioning would detect the newest tag, not the checked out tag. Look for the HEAD string prior to tag: to indicate the currently selected tag.
* Make the v-prefix optional in git semverZachary Hueras2015-09-161-1/+1
| | | | | | Not all repositories use a v-prefix for version tags. All tags should be considered valid versions.
* Modify parse_git_url to be more genericDavid Leach2015-08-111-14/+21
| | | | | | Changes parse_git url function to use Using RFC3986 standard to validate git uri instead of matching strings in function head. Also accepts scp style syntax for parsing.
* Escape paths and args in shell commandsFred Hebert2015-07-181-9/+19
| | | | | | | Basic escaping is done only. Fancy hex sequences are not covered, but this should otherwise take care of the most common issues. Fixes #497
* Fix missing 'cd' that depended on cwd changesFred Hebert2015-07-101-1/+3
|
* Only have the port cd, not rebar3 as a wholeFred Hebert2015-07-081-15/+10
|
* handle http:// git deps in check fif upgrade neededTristan Sloughter2015-07-061-0/+4
|
* Fix common test run duplication on windowsViacheslav Kovalev2015-06-261-1/+1
|
* fix rebar_git_resourcederwinlu2015-05-071-14/+16
| | | | | | * fix shell commands relying on non windows shell commands * fix shell commands using wrong quotes * implement native wc -l
* only fetch branch needed, remove rebar_vsn_plugins from erlware_commonsTristan Sloughter2015-05-031-1/+1
|
* on upgrade of git branch check against remoteTristan Sloughter2015-05-031-4/+7
|
* Fix typo in error messageViacheslav V. Kovalev2015-03-101-1/+1
|
* use rebar_utils:sh for git and hg commands to have better errors and logsTristan Sloughter2015-03-031-15/+32
|
* replace package management with hex.pmTristan Sloughter2015-02-171-9/+9
|
* needs_update: on ref defined deps only have to match prefix if 7+ charsTristan Sloughter2015-02-161-8/+15
|
* fixes for dialyzer findingsTristan Sloughter2014-11-301-6/+1
|
* fix git resource update check, bad url comparisonTristan Sloughter2014-11-221-14/+27
|
* handle throw by relxTristan Sloughter2014-11-081-6/+6
|
* properly reset cwd after finding version of git resourceTristan Sloughter2014-11-051-1/+1
|
* support branch/tag/ref-less git depsTristan Sloughter2014-11-051-2/+4
|
* add make_vsn to rebar_resource for replacing app vsnsTristan Sloughter2014-11-031-1/+66
|
* run legacy style hooks for compile providerTristan Sloughter2014-11-011-0/+2
|
* verify checked out dep is the same as specified in the config and update if notTristan Sloughter2014-11-011-1/+36
|
* create rebar_resource behaviour and create git resourceTristan Sloughter2014-10-301-0/+44
generated by cgit v1.1 at 2024-12-26 21:14:17 +0000