5 Commits

Author	SHA1	Message	Date
Eugene Vigdorchik	945fdd5baa	Use raw methods on URI where a single string representation is constructed. URI(String) assumes no special characters.	2012-06-15 07:54:14 -04:00
Eugene Vigdorchik	47c9645892	Use raw method not to unescape special characters. Fixes #478	2012-06-12 07:15:17 -04:00
Sanjin Sehic	972acc871a	Allow retrieving of non-standard git URIs ... Non-standard git URIs are ones that do not start with 'git:' nor end with '.git'. An example of non-standard git URI is 'ssh://server/home/user/repo'. The mechanism for specifying a non-standard git URI is done by prefixing the whole URI with 'git:' to signify that it should be handled with the git resolver. For example, non-standard git URIs like 'git:ssh://server/user/repo' and 'git:https://server/user/repo' can now be used.	2012-02-13 22:02:44 -05:00
Sanjin Sehic	77626f5232	Optimize retrieving from git repositories ... Instead of cloning from a remote git repository for each branch, revision or tag separately, the git resolver locally clones only once the remote git repository and then creates further local clones from this local copy of the remote repository. First, optimization, of course, is execution speed, because cloning local repository is much faster than remote repository. Furthermore, because git uses hard-linking when a clone of local repository is created, the second optimization is in space consumption. For example, if we have one project that uses https://github.com/harrah/xsbt.git#v0.11.1 and second project that uses https://github.com/harrah/xsbt.git#v0.11.2, in previous git resolver implementation it would require two separate clones of the remote git repository at https://github.com/harrah/xsbt.git. But, the new git resolver requires only one clone of the remote git repository and two local clones which take no space because of hard-linking.	2012-02-13 22:02:44 -05:00
Sanjin Sehic	942427bfa3	Extract local, remote, and git BuildLoader.Resolver from ResolveUnit	2012-02-13 22:02:44 -05:00