- 15 Mar, 2012 6 commits
-
-
Fabio Pelosin authored
-
Fabio Pelosin authored
appledoc options
-
Fabio Pelosin authored
* upstream/master: Fix .kick script for Kicker 2.5.0 Print a template for a new ticket when an error occurs. See #163.
-
Fabio Pelosin authored
- refactoring - default options for appledoc - added command line arguments to pod install - added option to force documentation generation with appledoc
-
Eloy Durán authored
-
Eloy Duran authored
-
- 14 Mar, 2012 4 commits
-
-
Fabio Pelosin authored
-
Fabio Pelosin authored
* upstream/master: Update for Xcodeproj HEAD. Don't validate the git repo settings, as the installer cleans it out.
-
Eloy Duran authored
-
Ben Scheirman authored
(Not sure which is correct behavior, but I assumed this test was wrong)
-
- 13 Mar, 2012 2 commits
-
-
Fabio Pelosin authored
- introduced '--generate_documentation' '--install_documentation' command line options - only doc installation/generation only if pod does not exists
-
Fabio Pelosin authored
-
- 08 Mar, 2012 2 commits
-
-
Fabio Pelosin authored
-
Fabio Pelosin authored
-
- 06 Mar, 2012 1 commit
-
-
Fabio authored
-
- 05 Mar, 2012 18 commits
-
-
Fabio authored
-
Luke Redpath authored
-
Luke Redpath authored
We don't need to use Tempfile anyway, we can stick the tarball in the pod root and then delete it.
-
Luke Redpath authored
-
Luke Redpath authored
-
Luke Redpath authored
-
Luke Redpath authored
-
Luke Redpath authored
Generally speaking, this should be much faster than cloning a repository (even a shallow one) and we can take take advantage of Github's tarball support. I've made this opt-in (using the :download_only option) in case this breaks any existing functionality people expect (e.g. using submodules).
-
Luke Redpath authored
-
Eloy Duran authored
-
Eloy Duran authored
-
Eloy Duran authored
-
Eloy Duran authored
-
Eloy Duran authored
-
Eloy Duran authored
-
Luke Redpath authored
Started adding some specs for the target installer, including for this fix.
-
Eloy Duran authored
-
Eloy Duran authored
-
- 04 Mar, 2012 7 commits
-
-
Eloy Duran authored
-
Eloy Duran authored
-
Eloy Duran authored
-
Luke Redpath authored
because previously each TargetInstaller would resolve it's specs separately. Instead, we resolve everything in one go as before, but have the resolver return a hash of target dependencies to resolved specifications, so when the target installers are run, we only install the pods for that target that should be in there. Likewise, we should only call the post-install hook of a specification with the target installers it belongs to.
-
Eloy Duran authored
-
Eloy Duran authored
-
Luke Redpath authored
-