summaryrefslogtreecommitdiff
path: root/test/rebar_deps_SUITE.erl
Commit message (Collapse)AuthorAgeFilesLines
* support for hex v2, multiple repository fetching, private organizations (#1884)Tristan Sloughter2018-09-131-68/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * update to hex_core for hex-v2 repo support (#1865) * update to hex_core for hex-v2 repo support This patch adds only single repo hex-v2 support through hex_core. Packages no longer filtered out by buildtool metadata and the package index is updated per-package instead of fetched as one large ets dump. * tell travis to also build hex_core branch * support list of repos for hex packages (#1866) * support list of repos for hex packages repos are defined under the hex key in rebar configs. They can be defined at the top level of a project or globally, but not in profiles and the repos configured in dependencies are also ignored. Searching for packages involves first checking for a match in the local repo index cache, in the order repos are defined. If not found each repo is checked through the hex api for any known versions of the package and the first repo with a version that fits the constraint is used. * add {repos, replace, []} for overriding the global & default repos * add hex auth handling for repos (#1874) auth token are kept in a hex.config file that is modified by the rebar3 hex plugin. Repo names that have a : separating a parent and child are considered organizations. The parent repo's auth will be included with the child. So an organization named hexpm:rebar3_test will include any hexpm auth tokens found in the rebar3_test organization's configuration. * move packages to top level of of hexpm cache dir (#1876) * move packages to top level of of hexpm cache dir * append organization name to parent's repo_url when parsing repos * only eval config scripts and apply overrides once per app (#1879) * only eval config scripts and apply overrides once per app * move new resource behaviour to rebar_resource_v2 and keep v1 * cleanup use of rebar_resource module and unused functions * cleanup error messages and unused code * when discovering apps support mix packages as unbuilt apps (#1882) * use hex_core tarball unpacking support in pkg resource (#1883) * use hex_core tarball unpacking support in pkg resource * ignore etag if package doesn't exist and delete if checksum fails * add back tests for bad package checksums * improve bad registry checksum error message
* Allow top-level apps to take precedence over depsFred Hebert2017-08-051-1/+29
| | | | | | | | | | | | | | | | | | | | | | | | The use case has been described in issue #1478 where a local application can exist while being declared as a dependency as well. This allows, for example, to work on a release where all applications may require to be published independently, or to provide some form of 'vendoring' with a local app. The fix is done by decoupling the dependency source resolution form the dependency parsing. The reason for this being that the discovery phase needs to parse apps for their top-level deps, and dep installation needs to resolve the packages with accuracy. In the current implementation, both code paths call to the same function. This patch splits up the precise discovery and makes it happen *only* when installing dependencies, and only if a top-level app does not already define the application needing resolving. One weakness of this fix is that it necessarily breaks cycle detection in dependencies that involve a root application depending on itself since its own version as a dep will not be expanded. There appears to be no possible way to prevent this, but should be rare enough to be worth the tradeoff for the common case.
* Properly support package aliasing and alt namesFred Hebert2016-09-271-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Aliasing only had a bit of ad-hoc support in rebar3, and various issues have encountered problems related to the package names not mapping properly with the application name. One such issue is https://github.com/erlang/rebar3/issues/1290 The problem has been hard to find because it only impacts transitive dependencies (not top-level ones) of other packages. The root cause for this is that the application name was not being tracked by rebar3's internal index, only the package name and its version were. When a given application was a package app, the data for the application name would be reconstructed from the lock file, but only if it were a top-level app or a dependency of a source application where parsing the lock file is necessary to know what comes next. When a transitive dependency of a package dependency was fetched, we instead read its dependencies directly from the in-memory package index within rebar3. This caused us to only read the package name and version, and lost all information regarding application name. This worked fine for most cases since for the vast majority of packages, the package name matches the app name, but failed for all aliases, which would then be moved to directories that wouldn't match the app name. This in turn broke some aspects of code analysis (in Dialyzer), or other functionality relying on static paths, such as including .hrl files from dependencies. This patch reformats the internal storage format of dependencies to align with the internal one used by rebar3, so that the app name can be carried along with the package name and its version. The fix can only work once `rebar3 update` is called so the index is rebuilt internally, and will the file cached on disk will be incompatible with older rebar3 versions. Currently, the following is not covered: - Tests - Including the package hashes of dependencies so they may match what is in a lock file -- they're being `undefined` instead, which may break some lookups. The previous format did not lend itself to hashing in the same way, and it is possible transitive deps were not being tracked properly, or worked by respecting the current package hierarchy. This will require further analysis For now this commit can allow reviewing and discussion.
* Merge pull request #1207 from ferd/pkg-local-hash-lockFred Hebert2016-06-221-1/+1
|\ | | | | lock file contains expected hash for pkg dependencies
| * Support package hashes in structure and lockfileFred Hebert2016-05-241-1/+1
| | | | | | | | | | | | | | | | | | - the internal representation for package locks moves from `{Name, {pkg, PkgName, Vsn}, Lvl}` to `{Name, {pkg, PkgName, Vsn, Hash}, Lvl}` - the internal representation for packages moves from `{pkg, PkgName, Vsn}` to `{pkg, PkgName, Vsn, Hash}` - the hash can be `undefined`, meaning no check will be done - no checking is done yet.
* | Support ENV config for proxy valuesFred Hebert2016-06-111-1/+72
|/ | | | | - The configured stuff in rebar3 takes precedence over the ENV - The env is then chosen
* Add more hex rules so they don't throw errorsHeinz N. Gies2016-02-221-18/+94
| | | | | | | | | | Add more version constraints Allow for any number of whitespaces after compairison opperator Improve updating and error printing Fix failing tests
* handle newly added deps to config even when lock is emptyTristan Sloughter2015-09-241-1/+33
|
* this patch treats pkg and src deps as equals, so level decides winnerTristan Sloughter2015-08-211-1/+1
| | | | | | | | Instead fetching and resolving src deps (which could depend on pkg deps) and then pkg deps this patch combines the two into a single set of iterations by level. The only difference between src and pkg deps in this new install_deps is how their deps list is found -- from the config or lock file for src deps and from the neighbors of the vertex for pkg.
* Add tests for mixed deps installsFred Hebert2015-08-161-24/+7
| | | | | Requires a rework of other test suites using the same dep-handling mechanism.
* install package deps in same level/profile order as src depsTristan Sloughter2015-08-131-2/+2
|
* only look for top level apps and those directly under apps/ or lib/Tristan Sloughter2015-07-161-2/+2
|
* Added version check based on commit ↵CarlosEDP2015-07-041-4/+7
| | | | https://github.com/ferd/rebar3/commit/74c68478aac948beccc80e68c5ac6a9eb578eceb
* Refactor tests to init/exec/end. Check OTP version to skip https test on OTP ↵CarlosEDP2015-07-031-39/+45
| | | | =< 15.
* Added testcases for http and https proxy use.CarlosEDP2015-07-031-1/+58
|
* check format of config file and print the bad section in the errorTristan Sloughter2015-06-181-1/+1
|
* basic profile deps testsTristan Sloughter2015-02-221-46/+14
|
* check for newly added deps in config file that aren't level 0 in the lockTristan Sloughter2015-02-191-4/+40
|
* use project sub-apps with deps in their rebar.configTristan Sloughter2015-02-171-1/+29
|
* replace package management with hex.pmTristan Sloughter2015-02-171-62/+187
|
* Initial `deps` commandFred Hebert2015-02-161-188/+62
|
* WIPFred Hebert2015-02-111-1/+0
| | | | | | Test that all the correct locks are set for an upgrade run. Now to actually re-run the install deps and prove it works
* Fix up programmatic interface to rebar3Fred Hebert2014-12-211-1/+1
| | | | Now supports arbitrary commands
* Adding pkg deps tests and refactoringsFred Hebert2014-12-161-26/+95
| | | | | | | | | | | | | | | | | | | - Adding tests for package deps - Adding conflict/override warnings for package deps - Adding cycle detection for packages - Adding cycle detection for mixed packages+source - Fixing internal dependency format of package resources when converted to rebar_app_info - normalizing level-order prioritization to be based on lexicographical sort of app names rather than traversal order (which is undefined for package deps) - Fixing tests for source deps for deep cycle detection - Fixing bugs with source deps - Relaxed version format checks for test utils A lot of fixes are combined in there because I didn't want to commit non-passing code, and many bugs were found when adding the second batch of tests as part of the original effort.
* Print warning when deps are being skipped.Fred Hebert2014-12-071-13/+64
| | | | | The case in mind here is due to conflicts, and tests have been added for this.
* Handle cycle errors in providerFred Hebert2014-12-061-2/+2
|
* Return cycles in deps solverFred Hebert2014-12-061-2/+2
|
* Partial fix to circular deps (#40)Fred Hebert2014-12-061-9/+26
| | | | | | | | | - Adding tests - fixing use of set fetching to find repeated deps and prevent infinite loops On a circular loop rebar3 now fails with `{error, no_sort}`, which is uncaught and should be handled to consider the issue fully fixed.
* Initial tests for dependency resolvingFred Hebert2014-12-041-0/+85
- Reworked the helpers for existing suites and expanded them - Created a mock git resource module to test for its dependency fetching - Added a test suite for dependency resolving with first checks for common cases (https://gist.github.com/ferd/197cc5c0b85aae370436) Left to do would include: - Verify warnings - Verify failures - Verify dependency updates resolving
generated by cgit v1.1 at 2024-12-26 04:56:27 +0000