summaryrefslogtreecommitdiff
path: root/lib/bundler/templates/newgem/newgem.gemspec.tt
Commit message (Collapse)AuthorAgeFilesLines
* Switch to double quotes to match rest of fileJonathan Hefner2019-10-141-2/+2
|
* Not sure how much this buys us, remove itremove_add_development_dependency_from_new_gemsDavid Rodríguez2019-06-261-2/+0
|
* Generate new gem development dependencies in GemfileDavid Rodríguez2019-06-261-7/+0
|
* Add `required_ruby_version` to gemspec templategemspec-rrMiklos Fazekas2019-06-171-0/+1
|
* Add `require_relative` to gemspec templateMiklos Fazekas2019-04-231-3/+1
|
* Remove ruby version leftoversremove_ruby_version_leftoversDavid Rodríguez2019-03-151-6/+0
|
* Bump rake version to 12.0 on gemspec template. Because rake-10.0 is EOL now.SHIBATA Hiroshi2019-01-241-1/+1
|
* Remove more unnecessary stuffremove_old_rubygems_stuff_from_specsDavid Rodríguez2018-10-261-11/+4
|
* bundle gem will generate homepage_uri and code and changelog section by defaultKeiji Yoshimi2018-09-141-0/+4
|
* Use `__dir__` instead of `__FILE__` in newgem.gemspec templateKoichi ITO2018-04-231-1/+3
| | | | | | | | | | | | | | | | | | | ### What was the end-user problem that led to this PR? Since Ruby 2.0 we've had `__dir__` as well as `__FILE__`. The initial gem codes written with `bundle gem` using Ruby 2.0 or higher is an old description using `__FILE__`. ### What was your diagnosis of the problem? Ruby 1.9 is EOL, so I think that there is not much Gem to start developed using it. ### What is your fix for the problem, implemented in this PR? This PR uses `__dir__` when starting Gem development (i.e. `bundle gem`) using Ruby 2.0 or higher version.
* Change commentsNikita Esaulov2018-03-161-1/+1
|
* Add a comment about default spec.files setupNikita Esaulov2018-03-161-0/+1
|
* Add a comment describing spec.files method in the .gemspec templateNikita Esaulov2018-03-151-0/+1
|
* Ensure git is executed inside the gemspec dirElia Schito2017-11-281-2/+2
| | | | | | | When a Gemfile was pointing to a local gem using git to list its files the git command was executed from within the wrong dir. This fixes the issue without: 1. introducing new dependencies (e.g. `shellwords`) 2. any risks with non-trivial paths (e.g. paths containing spaces)
* Remove a blank line in generated gemspec for RUBY_VERSION >= "2.0.0"meganemura2017-10-271-1/+1
|
* Add new line after new gem gemspec templateRobert Soly2017-07-311-0/+1
|
* Tweak gemspec template when using Ruby 2.xKoichi ITO2017-07-031-0/+2
|
* Unify the notation of RubyGemsKoichi ITO2017-05-041-1/+1
|
* Add spaces around ERB tagsZach Ahn2017-03-051-7/+7
|
* Switch newgem template single quotes to double quotesZach Ahn2017-03-041-3/+3
|
* Fix 80 column on newgem gemspecLaurent Arnoud2016-03-291-2/+5
|
* Clarify comment in `bundle gem` gemspecJosh Bodah2016-02-041-2/+2
| | | | | The comment feels a bit misleading. It sounds like this allows Rubygems pushes by default which it does not
* Pessimistic test framework versions for bundle gem commandTim Fischbach2015-07-271-1/+1
| | | | | | | | | | Use a pessimistic version requirement for RSpec and Minitest in gemspecs generated by the `bundle gem` command. It is best practice to at least depend on major versions of development dependency gems. * Hard code major versions of the two testing frameworks. * Add a spec that tests that only specific version requirements are used in development dependencies.
* remove logic that checks for string 'false' in template (depends on b397724)Rose Weixel2015-07-261-1/+1
|
* Merge tag 'v1.9.4'Andre Arko2015-04-131-4/+8
| | | | | | | | Version 1.9.4 Conflicts: lib/bundler/installer.rb lib/bundler/match_platform.rb lib/bundler/source/rubygems.rb
* Merge tag 'v1.8.5'Andre Arko2015-03-111-4/+6
|\ | | | | | | | | | | | | | | Version 1.8.5 Conflicts: lib/bundler/templates/newgem/newgem.gemspec.tt lib/bundler/version.rb
| * remove MIT license from gemspec if not configuredAndre Arko2015-03-111-4/+6
| |
* | Allow dev versions when creating a new gem.Tim Moore2015-02-181-1/+1
|/
* Set spec.bindir to the new executables location.Tim Moore2015-02-131-0/+1
|
* move gem bins to exe/ and add console and setupAndre Arko2015-01-251-4/+4
|
* Extended gem generation and generation settingsKir Shatrov2015-01-251-1/+1
| | | | | | | | | | | | | As discussed in https://github.com/bundler/bundler/pull/3305#issuecomment-67024669, the gem generator should not generate default files that change the rights or responsibilities of gem authors without their explicit consent. Let's change the gem generator to ask gem authors what they want, and allow them to change it via config or --flags. * Remove LICENSE from default gem * Remove CODE_OF_CONDUCT from default gem * Add --coc flag to generate CODE_OF_CONDUCT * Add --mit flag to generate LICENSE * On gem generation, if not set to true/false, ask user if they are willing to license their code permissively under the MIT license * On gem generation, if not set to true/false, ask user if they are willing to add a Code of Conduct to their gem * On gem generation, if not set to false/rspec/minitest, ask if the user would like to generate tests along with their gems. Save the answer as bundle config gem.tests. * Ensure that --coc, --mit, --test flags overrule any config settings that may be set.
* Merge pull request #3116 from grosser/grosser/metadataAndré Arko2014-10-191-4/+3
|\ | | | | prevent all new gems to be rubygems 2.0 only
| * prevent all new gems to be rubygems 2.0 onlygrosser2014-07-271-4/+3
| |
* | Don't package test files with gemErik Michaels-Ober2014-10-081-2/+1
|/
* balance the erb tag dashesAndre Arko2014-05-111-7/+7
|
* describe what homepage is for, tooAndre Arko2014-05-111-1/+1
|
* don't describe the noun, offer actionsAndre Arko2014-05-111-2/+2
| | | | /cc @zzak
* Add more explanation to spec.description for bundle gem template.Zachary Scott2014-05-091-1/+1
| | | | | | | | | "Optional" sounds like you can leave this value unchanged, but will raise an exception in this case, aborting before the gem is built: WARNING: See http://guides.rubygems.org/specification-reference/ for help ERROR: While executing gem ... (Gem::InvalidSpecificationException) "FIXME" or "TODO" is not a description
* depend on rake 10.x, semanticallyAndre Arko2014-05-051-1/+1
| | | makes rubygems happy
* clean up allowed_gem_host testAndre Arko2014-05-051-1/+2
| | | | | | - use a Gem::Requirement - change to Rubygems 2.0, when metadata support was added - depend on Rubygems 2.0 or greater - add test metadata support for Rubygems 2.0-2.2
* Add allowed_push_host to new gem template if rubygems >= 2.2.0.Juanito Fatas2014-05-011-0/+5
|
* Added the --ext option to the gem command. This generates a skeleton for C ↵Andre Medeiros2014-03-021-0/+6
| | | | extensions.
* Merge tag 'v1.5.2' into 'master'Andre Arko2014-01-101-1/+1
| | | | | | | | | | Conflicts: CHANGELOG.md Rakefile lib/bundler/installer.rb lib/bundler/rubygems_ext.rb lib/bundler/source/rubygems.rb spec/realworld/parallel_install_spec.rb spec/realworld/parallel_update_spec.rb
* gemspec template: clarify summary vs description.Henrik Nyh2013-09-111-2/+2
| | | I never remember which is which, so I clarified based on http://guides.rubygems.org/specification-reference/.
* fix dep name, add version constraintAndre Arko2013-02-021-1/+1
|
* Add bundler itself as a default development dependencyErik Michaels-Ober2013-02-021-0/+1
|
* Use canonical name for block localErik Michaels-Ober2013-02-021-15/+15
| | | | | Makes template consistent with examples in http://docs.rubygems.org/read/chapter/20
* Don't depend on git in gemspecErik Michaels-Ober2013-02-021-1/+1
|
* Add gem for testing as a development dependencyRyunosuke SATO2013-01-171-0/+3
|
* simplify newgem.gemspec.tt, grep need no mapTimo Schilling2012-12-191-1/+1
|
View Lorry Controller Status