Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Duplicate --no-update Option #725

Closed
GWStuartClift opened this Issue Jan 8, 2013 · 4 comments

Comments

Projects
None yet
3 participants

When using pod update --help the --no-update command is appended twice for the Class Update as it is also inherited from its super Class Install

Trivial issue and fix, although looksClass Update will be gone in 0.17 anyway.

Owner

alloy commented Jan 10, 2013

I’ll see if I can sneak it in before 0.17.

Owner

fabiopelosin commented Jan 10, 2013

I think that this issue should be already resolved in 0.17 as we introduced CLAide. Lets leave the ticket open in order to remember to check.

@alloy alloy closed this in 3efdcda Jan 13, 2013

Owner

alloy commented Jan 13, 2013

Yup, it already works good in 0.17, but it was small enough to fix until then :)

Owner

alloy commented Jan 13, 2013

Just released in 0.16.1

@fabiopelosin fabiopelosin added a commit that referenced this issue Jan 15, 2013

@fabiopelosin fabiopelosin Merge branch 'master' into 0.17
* master:
  Update README.md
  Release 0.16.1
  [Gemspec] Bump Xcodeproj to 0.4.1
  [CHANGELOG] Update for Xcodeproj 0.4.1 and CocoaPods 0.16.1
  Update bundle and make specs green.
  [Update Command] Remove duplicate option in help. Closes #725.
  Update previous patch to match code-style.
  Unpack tgz files into pod's root #727
  If a repo isn't passed to push default to master

Conflicts:
	CHANGELOG.md
	Gemfile.lock
	cocoapods.gemspec
	lib/cocoapods.rb
	lib/cocoapods/command/push.rb
	lib/cocoapods/command/update.rb
	lib/cocoapods/downloader/http.rb
	spec/functional/downloader_spec.rb
	spec/unit/http_spec.rb
0ba09e1

@jzapater jzapater pushed a commit to jzapater/CocoaPods that referenced this issue Sep 17, 2013

@jacobjennings jacobjennings Merge pull request #725 from jacobjennings/master
Add FXLabel version 1.3.7
bb7c063
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment