technicalpickles / jeweler

Opinionated tool for creating and managing Rubygem projects — Read more

Sort By: Priority | Votes | Last Updated

Loading…

20.

2 votes

bug
x

The Umlaut problem: UTF-8 chars get converted to unicode entities
4 comments Created 7 months ago by Soleone
When using an UTF-8 character (like the german umlaut ü) in the Rakefile, it gets converted to (2!) UTF-8 entities it seems.

For example in Rakefile it reads:
```
gem.authors = ["Markus Hüberman"]
```
And in the resulting gemspec file after releasing it gets converted to:
```
s.authors = ["Markus H\303\274berman"]
```
Comments
technicalpickles Tue Jul 07 22:07:39 -0700 2009 | link

I'm not super familiar with UTF-8 in general, so I'm not sure I can fix this myself.

I've found some notes about doing a File.open to write as utf-8, but it seems to be Ruby 1.9 specific.

Comment
I'm not super familiar with UTF-8 in general, so I'm not sure I can fix this myself. I've found some notes about doing a File.open to write as utf-8, but it seems to be Ruby 1.9 specific.
or cancel

Chastell Fri Nov 27 15:23:09 -0800 2009 | link

Hm, I’m using Ruby 1.9 and UTF-8 in my summary field and both the gemspec file and the resulting gem’s metadata contain the proper UTF-8 strings – i.e., this bug does not manifest itself in my case.

Markus: I tried your name in my gem and it worked. Did you specify the right Ruby file encoding (my Rakefile’s first line is ‘# encoding: UTF-8’)?

Comment
Hm, I’m using Ruby 1.9 and UTF-8 in my summary field and both the gemspec file and the resulting gem’s metadata contain the proper UTF-8 strings – i.e., this bug does not manifest itself in my case. Markus: I tried your name in my gem and it worked. Did you specify the right Ruby file encoding (my Rakefile’s first line is ‘# encoding: UTF-8’)?
or cancel
Chastell Fri Nov 27 15:26:24 -0800 2009 | link
BTW: \303\274 is the proper binary representation of UTF-8 ü:

>> "Markus Hüberman" == "Markus H\303\274berman" => true
Comment
BTW: \303\274 is the proper binary representation of UTF-8 ü: >> "Markus Hüberman" == "Markus H\303\274berman" => true
or cancel
SFEley Mon Jan 25 10:14:41 -0800 2010 | link

It would make sense for the generated Rakefile to add # encoding: UTF-8 as its first line. This is harmless in Ruby 1.8 but very important in Ruby 1.9 for consistency.

Comment
It would make sense for the _generated_ Rakefile to add `# encoding: UTF-8` as its first line. This is harmless in Ruby 1.8 but very important in Ruby 1.9 for consistency.
or cancel

Please log in to comment.
46.

0 votes

Push to local gem repository
4 comments Created 3 months ago by tmeasday

Have you considered adding support for local gem repositories into jeweler somehow?

i.e. something like: http://blog.martiandesigns.com/2008/10/08/creating-a-simple-private-gem-repository/

It would be cool to have a rake gem:release:local task to scp the build gem across and ssh in and run the gem generate_index command.

Comments

technicalpickles Fri Oct 16 08:07:53 -0700 2009 | link

No, I hadn't considered, because I don't use local gem repositories.

I don't see this as something I'd implement myself, but if there was a fork... and it followed the same paradigms for releasing, well maybe a merge might happen.

Comment
No, I hadn't considered, because I don't use local gem repositories. I don't see this as something I'd implement myself, but if there was a fork... and it followed the same paradigms for releasing, well maybe a merge might happen.
or cancel

jrun Sun Jan 17 13:33:45 -0800 2010 | link

I've looked into this a bit. After looking at rubygems and gemcutter there isn't much jeweler needs to do other then set the env variable RUBYGEMS_HOST.

gem push (which jeweler uses for releasing to gemcutter) should just work then.

As for the server, you can run your own gemcutter server. It is easy to setup. I am also debating whether or not it is worthwhile to write a light weight, database free, gemcutter api compatible gem server. Again, that should allow for client tools like jeweler to just work.

Comment
I've looked into this a bit. After looking at rubygems and gemcutter there isn't much jeweler needs to do other then set the env variable [RUBYGEMS_HOST](http://github.com/qrush/rubygems/blob/gemcutter/lib/rubygems/command.rb#L373). `gem push` (which jeweler uses for releasing to gemcutter) _should_ just work then. As for the server, you can run your own gemcutter server. It is easy to setup. I am also debating whether or not it is worthwhile to write a light weight, database free, gemcutter api compatible gem server. Again, that _should_ allow for client tools like jeweler to just work.
or cancel

shadowbq Mon Jan 25 15:30:52 -0800 2010 | link

I do this all the time now.. it works just fine.

GEMCUTTER_URL=https://gemcutter.myinternal.domain gem push ./pkg/supergem.gem

Comment
I do this all the time now.. it works just fine. GEMCUTTER_URL=https://gemcutter.myinternal.domain gem push ./pkg/supergem.gem
or cancel

technicalpickles Mon Jan 25 21:25:10 -0800 2010 | link

If that works, you should be able to do GEMCUTTER_URL="blah" rake gemcutter:release as well.

Comment
If that works, you should be able to do `GEMCUTTER_URL="blah" rake gemcutter:release` as well.
or cancel

Please log in to comment.
47.

0 votes

waiting for release
x

Allow jeweler and gemspec to be agnostic (you can use rake or thor)
3 comments Created 3 months ago by josevalim

Thor is able to wrap Rake tasks, so I can use Jeweler with it. The only downside is that my gemspec keeps a note to Rakefile, which does not exist, since we are using a Thorfile. I've created a small patch that allows it to detect whether a Rakefile or a Thorfile are being used.

http://github.com/josevalim/jeweler

Since I was there, I also removed mention to Github building gems.

Regards!

Comments

technicalpickles Sun Oct 18 20:04:59 -0700 2009 | link

Merged.

I'd also like to see more proper thor support. I started using your Thorfile in thor as an example, but I'm not sure how you're actually supposed to run it. You can see it in the 'thor' branch.

Comment
Merged. I'd also like to see more proper thor support. I started using your Thorfile in thor as an example, but I'm not sure how you're actually supposed to run it. You can see it in the 'thor' branch.
or cancel

georgeguimaraes Mon Oct 19 09:21:02 -0700 2009 | link

Thor uses the name of the class as namespace, so you should run the gemspec task as:

thor default:gemspec

However, the default namespace can be a shortcut, so you need just do:

thor :gemspec

If that doesn't work, I will take a look at it when I'm back home. Also, you don't need the require 'spec/rake/spectask' at the top. :)

Thanks!

Comment
Thor uses the name of the class as namespace, so you should run the gemspec task as: thor default:gemspec However, the default namespace can be a shortcut, so you need just do: thor :gemspec If that doesn't work, I will take a look at it when I'm back home. Also, you don't need the require 'spec/rake/spectask' at the top. :) Thanks!
or cancel

georgeguimaraes Mon Oct 19 09:22:27 -0700 2009 | link

Ok, the comment above was done by @josevalim. ;)

Comment
Ok, the comment above was done by @josevalim. ;)
or cancel

Please log in to comment.
48.

0 votes

jeweler doesn't work with the newest version of reek
4 comments Created 3 months ago by priteau

I have reek version 1.2.2 installed.
rake reek returns:
"Reek is not available. In order to run reek, you must: sudo gem install reek"

That's because the Rakefile generated by jeweler does a require 'rake/testtask', but the file moved
(see http://wiki.github.com/kevinrutherford/reek/rake-task)

Comments

technicalpickles Tue Oct 20 07:53:09 -0700 2009 | link

I think you mean it does a require of 'reek/rake_task', not 'rake/testtask', right?

That being the case, I'm not sure what could be done to fix this. Sure, the generator can be fixed, but there's some people that would have generated their project already and have the old require.

Comment
I think you mean it does a require of 'reek/rake_task', not 'rake/testtask', right? That being the case, I'm not sure what could be done to fix this. Sure, the generator can be fixed, but there's some people that would have generated their project already and have the old require.
or cancel

priteau Tue Oct 20 08:10:36 -0700 2009 | link

Yes, sorry, I don't know why I didn't do a copy/paste...

I think you could support both versions in the generator (by rescuing the LoadError exception and retrying with the other path).

For the problem of already generated projets, I think it's really another bug: one should be able to update its jeweler-generated Rakefile to get modifications of the template, or even add new targets (for example someone should be able to add the reek target if the project was generated without it).

Comment
Yes, sorry, I don't know why I didn't do a copy/paste... I think you could support both versions in the generator (by rescuing the LoadError exception and retrying with the other path). For the problem of already generated projets, I think it's really another bug: one should be able to update its jeweler-generated Rakefile to get modifications of the template, or even add new targets (for example someone should be able to add the reek target if the project was generated without it).
or cancel

technicalpickles Tue Oct 20 10:20:35 -0700 2009 | link

Doing a begin/rescue within a begin/rescue to support both requires seems a little messy.

Considering this is a generator, I think it'd make sense to go with the most recent version, and just make sure the error message tells you to install the specific version that starts using the different task require.

Comment
Doing a begin/rescue within a begin/rescue to support both requires seems a little messy. Considering this is a generator, I think it'd make sense to go with the most recent version, and just make sure the error message tells you to install the specific version that starts using the different task require.
or cancel

technicalpickles Tue Oct 20 14:09:11 -0700 2009 | link

A non-jeweler specific fix would be to patch reek to put back the old file, and do a deprecation warning.

Comment
A non-jeweler specific fix would be to patch reek to put back the old file, and do a deprecation warning.
or cancel

Please log in to comment.
50.

0 votes

waiting for release
x

allow for extensions
3 comments Created 3 months ago by rdp

if there are files in the ext directory, typically it'll be
ext/
extconf.rb (Sometimes it's called mkrf_conf.rb) some_file.c some_other_file.c

I'd move that those

be added as extensions. Though I suppose the user could add them in manually, now that I think about it...

-r

Comments

technicalpickles Sun Nov 01 17:48:07 -0800 2009 | link

Fixed in cee2d7c, thanks for reporting!

Comment
Fixed in cee2d7c0c11e42339d0ed01a3bc024d35d4d831c, thanks for reporting!
or cancel

rdp Mon Nov 02 10:05:32 -0800 2009 | link

any possibility for mkrf_conf.rb love in there, as well?
Thanks!

Comment
any possibility for mkrf_conf.rb love in there, as well? Thanks!
or cancel

technicalpickles Mon Nov 02 10:22:11 -0800 2009 | link

I don't even know what you mean... As far as I can tell, gem only cares about extconf.rb.

Comment
I don't even know what you mean... As far as I can tell, gem only cares about extconf.rb.
or cancel

Please log in to comment.
54.

0 votes

Support for gem bundler
7 comments Created 3 months ago by jsmestad
Ran into this issue when using bundler with jeweler. Bundler uses the ./bin directory for all its local executables and Jeweler assumes that the old standard that anything in the ./bin file in a gem should be packaged with the gem.

I think a good enhancement to the Jeweler generator would be to either add a flag for --with-bundler and then stub out: gem.executables = []

Comments
technicalpickles Wed Nov 04 15:44:35 -0800 2009 | link

So, I'm not opposed to seeing bundler support (in fact, would like to see it).

However, I don't particularly like it placing gems into bin/. I just feel like that'd have some annoyances, like you'd have to start git ignoring stuff in bin, except for things that you'd want distributed, in addition to specifying them in gem.executables.

Perhaps bundler can be configured where it places the binaries?

Comment
So, I'm not opposed to seeing bundler support (in fact, would like to see it). However, I don't particularly like it placing gems into `bin/`. I just feel like that'd have some annoyances, like you'd have to start git ignoring stuff in bin, except for things that you'd want distributed, in addition to specifying them in gem.executables. Perhaps bundler can be configured where it places the binaries?
or cancel
jsmestad Wed Nov 04 16:06:08 -0800 2009 | link
This is possible.

# Specify where gem executables should be copied to. # # This is an optional setting. # The default is: bin bin_path "my/executables"
Comment
This is possible. # Specify where gem executables should be copied to. # # This is an optional setting. # The default is: bin bin_path "my/executables"
or cancel
technicalpickles Wed Nov 04 16:38:17 -0800 2009 | link
That's good. So, I'd think it's make sense to have them in bin/vendor, vendor/bin, something along those lines. That mean...

The generator creates Gemfile

Gemfile species a path for the executables that not in bin

gitignores this path
Comment
That's good. So, I'd think it's make sense to have them in bin/vendor, vendor/bin, something along those lines. That mean... * The generator creates Gemfile * Gemfile species a path for the executables that not in bin * gitignores this path
or cancel
jsmestad Wed Nov 04 23:53:46 -0800 2009 | link

yeah. ill fork and implement.

Comment
yeah. ill fork and implement.
or cancel

jsmestad Thu Nov 05 13:34:06 -0800 2009 | link

I went with the following:

--bundler flag to the generator

use ./gbin for the bundled gem path

add both ./vendor and ./gbin to .gitignore.

Commits viewable on: http://github.com/jsmestad/jeweler/tree/bundler_support

Comment
I went with the following: `--bundler` flag to the generator use `./gbin` for the bundled gem path add both `./vendor` and `./gbin` to .gitignore. Commits viewable on: http://github.com/jsmestad/jeweler/tree/bundler_support
or cancel

technicalpickles Sun Nov 08 16:32:39 -0800 2009 | link

I've thought about it a little and I'm trying to figure out the use case for using this.

Is it for managing dependencies of a gem? If so, you'd still need need to manage those in the gemspec.

Comment
I've thought about it a little and I'm trying to figure out the use case for using this. Is it for managing dependencies of a gem? If so, you'd still need need to manage those in the gemspec.
or cancel

jsmestad Sun Nov 08 16:34:54 -0800 2009 | link

It makes it easy to fork a gem and just run ./bin/rake spec after doing gem bundle. Also the Gemfile manages all your gem dependencies at the same time. I added a rake hook that sets up the gemspec dependencies as well: http://github.com/jsmestad/jeweler/blob/bundler_support/lib/jeweler/templates/jeweler_tasks.erb#L13

Comment
It makes it easy to fork a gem and just run `./bin/rake spec` after doing `gem bundle`. Also the Gemfile manages all your gem dependencies at the same time. I added a rake hook that sets up the gemspec dependencies as well: http://github.com/jsmestad/jeweler/blob/bundler_support/lib/jeweler/templates/jeweler_tasks.erb#L13
or cancel

Please log in to comment.
55.

0 votes

better support for .document
0 comments Created 3 months ago by technicalpickles

Was informed on IRC:

argv[0]: technicalpickles put a '-' on a separate line followed by all the non ruby files, that way yard picks em up properly. rdoc does too ( just checked )

Comments

Please log in to comment.
57.

0 votes

Incomplete paragraph in "Customizing your project's gem specification" wiki page
1 comment Created 3 months ago by agrimm

The paragraph "... you are probably wondering where version is set. Jeweler manages the" in the wiki has an incomplete sentence. (I couldn't find the equivalent of a "Talk" page for github's wikis)

Comments

technicalpickles Fri Nov 06 20:51:33 -0800 2009 | link

The page in question is at http://wiki.github.com/technicalpickles/jeweler/customizing-your-projects-gem-specification for reference.

Will take a look at it soon.

Comment
The page in question is at http://wiki.github.com/technicalpickles/jeweler/customizing-your-projects-gem-specification for reference. Will take a look at it soon.
or cancel

Please log in to comment.
59.

0 votes

override user.name and user.email by ENV variables
0 comments Created 2 months ago by blindgaenger

According to git help config you can override user.name and user.email by $GIT_AUTHOR(NAME|EMAIL) and $GIT_COMMITER(NAME|EMAIL), which I did. Currently jeweler failes if they aren't set in ~/.gitconfig file.

Fixed in: http://github.com/blindgaenger/jeweler/tree/a12e0847b28c19313cae740b167d239d1335e528

Comments

Please log in to comment.
64.

1 vote

rake install command fails with Rubinius
8 comments Created 2 months ago by dkubb

The following line of code will fail with Rubinius:

http://github.com/technicalpickles/jeweler/blob/master/lib/jeweler/commands/install_gem.rb#L19

The reason is that Config::CONFIG['RUBY_INSTALL_NAME'] returns the string "rbx", but the code assumes it will be "ruby". A better solution would be to change this line to:

"#{Config::CONFIG['RUBY_INSTALL_NAME']} -S gem"

Which should work with all ruby implementations, regardless of the name of the binary.

Comments

technicalpickles Thu Nov 26 13:05:39 -0800 2009 | link

That sounds pretty reasonable. If you want to expedite it, patches are certainly welcome :)

Comment
That sounds pretty reasonable. If you want to expedite it, patches are certainly welcome :)
or cancel

dkubb Thu Nov 26 20:56:24 -0800 2009 | link

A pull request is on it's way. :)

Comment
A pull request is on it's way. :)
or cancel

dkubb Fri Nov 27 10:42:55 -0800 2009 | link

I've implemented the fix for this, and also fixed some failing specs in my fork:

http://github.com/dkubb/jeweler

Comment
I've implemented the fix for this, and also fixed some failing specs in my fork: http://github.com/dkubb/jeweler
or cancel

myabc Wed Dec 09 08:04:26 -0800 2009 | link

The current implementation also causes problems for installation with JRuby on Windows. There is no jgem.bat script on Windows.

Comment
The current implementation also causes problems for installation with JRuby on Windows. There is no jgem.bat script on Windows.
or cancel

dkubb Wed Dec 09 11:05:06 -0800 2009 | link

@myabc: Does the fix I've implemented resolve the JRuby on Windows problems?

Comment
@myabc: Does the fix I've implemented resolve the JRuby on Windows problems?
or cancel

myabc Wed Dec 09 12:18:19 -0800 2009 | link

@dkubb. Yes, it should do. The only thing I've been trying to check is compatibility with the up-coming IronRuby implementation (which does have an igem script, but I don't see the -S option in its documentation).

Comment
@dkubb. Yes, it should do. The only thing I've been trying to check is compatibility with the up-coming IronRuby implementation (which does have an `igem` script, but I don't see the `-S` option in its documentation).
or cancel

myabc Fri Dec 11 11:06:31 -0800 2009 | link

For IronRuby support, I chatted with jimmysch and they will look to implement the -S option: http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=3290

Comment
For IronRuby support, I chatted with jimmysch and they will look to implement the `-S` option: http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=3290
or cancel

myabc Mon Jan 04 04:44:04 -0800 2010 | link

This is now implemented in IronRuby too! http://twitter.com/jschementi/status/7365249412

Comment
This is now implemented in IronRuby too! http://twitter.com/jschementi/status/7365249412
or cancel

Please log in to comment.
65.

0 votes

Bumping version adds a trailing newline character in VERSION
0 comments Created 2 months ago by ilpoldo
Bumping version adds a trailing newline character in the VERSION file
If you use the snippet from the generated Rakefile to extract the gem version:
```
version = File.exist?('VERSION') ? File.read('VERSION') : ""
```
..you'll end up with a string that goes like:
```
File.read("VERSION")
# => "0.1.0\n"
```
Comments

Please log in to comment.
66.

0 votes

Jeweler::GemcutterTasks.new Throwing Ruby error
1 comment Created 2 months ago by Nevynxxx

Including the line Jeweler::GemcutterTasks.new, in the rake task causes Rake to fail with:

rake aborted!
wrong number of arguments (1 for 0)

Commenting this line out, but leaving the rest works as intended.

With trace the error is:

$ rake -I./lib -T --trace rake aborted!
wrong number of arguments (1 for 0)
/usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/specification.rb:53:in block in set_jeweler_defaults' /usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/specification.rb:44:inchdir' /usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/specification.rb:44:in set_jeweler_defaults' /usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler.rb:33:ininitialize' /usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/tasks.rb:43:in new' /usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/tasks.rb:43:injeweler' /usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/tasks.rb:11:in jeweler' /usr/lib/ruby19/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/gemcutter_tasks.rb:20:ininitialize' /home/anthony/Personal/Projects/wxRuby/wxRCG/tasks/gemcutter.rake:15:in new' /home/anthony/Personal/Projects/wxRuby/wxRCG/tasks/gemcutter.rake:15:in' /usr/lib/ruby19/gems/1.9.1/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:145:in load' /usr/lib/ruby19/gems/1.9.1/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:145:inblock in load_with_new_constant_marking' /usr/lib/ruby19/gems/1.9.1/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:521:in new_constants_in' /usr/lib/ruby19/gems/1.9.1/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:145:inload_with_new_constant_marking' /home/anthony/Personal/Projects/wxRuby/wxRCG/Rakefile:10:in block in <top (required)>' /home/anthony/Personal/Projects/wxRuby/wxRCG/Rakefile:10:ineach' /home/anthony/Personal/Projects/wxRuby/wxRCG/Rakefile:10:in <top (required)>' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:inload' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in raw_load_rakefile' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2017:inblock in load_rakefile' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in standard_exception_handling' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2016:inload_rakefile' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2000:in block in run' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:instandard_exception_handling' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1998:in run' /usr/lib/ruby19/gems/1.9.1/gems/rake-0.8.7/bin/rake:31:in' /usr/bin/rake:19:in load' /usr/bin/rake:19:in'

Versions:
$ ruby --version ruby 1.9.1p243 (2009-07-16 revision 24175) [i686-linux]
$ gem list

LOCAL GEMS

actionmailer (2.3.5, 2.3.4, 2.3.3)
actionpack (2.3.5, 2.3.4, 2.3.3)
activerecord (2.3.5, 2.3.4, 2.3.3, 2.2.2)
activeresource (2.3.5, 2.3.4, 2.3.3)
activesupport (2.3.5, 2.3.4, 2.3.3, 2.2.2)
authlogic (2.1.3, 2.1.2)
freelancing-god-thinking-sphinx (1.2.11)
gemcutter (0.1.8, 0.1.6)
git (1.2.5, 1.2.4)
jeweler (1.4.0, 1.3.0, 1.2.1)
json_pure (1.2.0, 1.1.9)
mislav-will_paginate (2.3.11)
mysql (2.8.1)
net-scp (1.0.2)
net-ssh (2.0.16, 2.0.15)
nifty-generators (0.3.0)
ocra (1.1.3)
pg (0.8.0)
rack (1.0.1, 1.0.0)
rails (2.3.5, 2.3.4, 2.3.3)
rake (0.8.7)
rubigen (1.5.2)
rubyforge (2.0.3, 2.0.2, 1.0.4)
rubygems-update (1.3.5)
rubyzip (0.9.1)
sqlite3-ruby (1.2.5)
svn2git (1.3.1)
wx_sugar (0.1.22)
wxruby (2.0.1, 2.0.0)
wxruby-ruby19 (2.0.1, 2.0.0)
xdg (0.5.2)

Comments

TylerRick Fri Jan 15 13:25:42 -0800 2010 | link

I don't know about you, but the problem for me was that I was using a modified version of the 'git' gem (I had the path to it in my RUBYLIB) and it had a different api for one of the methods called on this line:
self.files = (repo.ls_files(base_dir).keys - repo.lib.ignored_files).map do |file|

Looks like your error was on the same line...

wrong number of arguments (1 for 0)
/var/lib/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/specification.rb:53:in `block in set_jeweler_defaults'

Comment
I don't know about you, but the problem for me was that I was using a modified version of the 'git' gem (I had the path to it in my RUBYLIB) and it had a different api for one of the methods called on this line: self.files = (repo.ls_files(base_dir).keys - repo.lib.ignored_files).map do |file| Looks like your error was on the same line... wrong number of arguments (1 for 0) /var/lib/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/specification.rb:53:in `block in set_jeweler_defaults'
or cancel

Please log in to comment.
68.

1 vote

Duplicate normalize_files line in gemspec_helper
0 comments Created 2 months ago by harrisj
In gemspec_helper.rb's #to_ruby method:
```
def to_ruby
  normalize_files(:files)
  normalize_files(:files)
  normalize_files(:extra_rdoc_files)
```
I think you want the second line to be normalize_files(:test_files)
Comments

Please log in to comment.
69.

0 votes

Generated .gemspec includes itself in files
2 comments Created 2 months ago by AlekSi

$ cat some_gem.gemspec ... s.files = ["fs-snapshot.gemspec", ...]
...

Comments

technicalpickles Fri Dec 04 08:55:23 -0800 2009 | link

Although it's kinda weird, I'm not sure if it's actually a bad thing.

Has this caused you any problems?

Comment
Although it's kinda weird, I'm not sure if it's actually a bad thing. Has this caused you any problems?
or cancel

AlekSi Tue Dec 08 21:36:33 -0800 2009 | link

No problems, but yes, it's weird.

Comment
No problems, but yes, it's weird.
or cancel

Please log in to comment.
73.

2 votes

Jeweler uses unsupported Ruby code in Gem Specification
1 comment Created 2 months ago by luislavena
Hello,

I'm the developer of rake-compiler, a rake helper that provides a glue and simplify the task of creation Ruby C extensions and binary gems across platforms.

In my role, I've received several reports of issues integrating Jeweler in the process of packaging and releasing those gems.

What rake-compiler does is take the original Gem Specification and duplicate it to allow generation of both pure-ruby gem (the default) and native ones for the platform you're targeting.

All this approach worked for scenarios of manually created gemspec or ones created with Hoe, but not Jeweler.

After further investigation, it seems Jeweler is defining 3 collection elements in the specification as Rake::FileList, something that is not supported by normal to_ruby code.

To simply prove my case, after a
```
Jeweler::Tasks.new
```
block:
```
g = Rake.application.jeweler.gemspec.dup
puts g.to_ruby
```
Generates the following output:
```
rake aborted!
ruby_code case not handled: Rake::FileList
C:/Users/Luis/Tools/Ruby/ruby-1.8.6-p383-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/specification.rb:1025:in `ruby_code'
C:/Users/Luis/Tools/Ruby/ruby-1.8.6-p383-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/specification.rb:737:in `to_ruby'
C:/Users/Luis/Tools/Ruby/ruby-1.8.6-p383-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/specification.rb:732:in `each'
C:/Users/Luis/Tools/Ruby/ruby-1.8.6-p383-i386-mingw32/lib/ruby/site_ruby/1.8/rubygems/specification.rb:732:in `to_ruby'
C:/Users/Luis/Projects/_sandbox/test/clean-gem/Rakefile:56
```
Which clearly shows the unsafe nature of defining files, test_files and extra_rdoc_files as FileList

While Jeweler parses and beautify
```
to_ruby
```
implementation, sanitizing it, the gemspec offered at the execution time is invalid, while the one stored in the gemspec file is.
I believe files, test_files and extra_rdoc_files should materialize as arrays in the gemspec sooner than the current delay implemented in your codebase.

For the record, the gemspec that is stored in the metadata part of a gem is in YAML format, not Ruby, so marshaling out from it generate the issues.

Thank you for your time.
Comments

myabc Tue Dec 08 06:09:21 -0800 2009 | link

@technicalpickles I tried to explain this issue in the IRC #jeweler channel the other evening, but thankfully luislavena has managed to state it much more coherently. In any case, we have a workaround for DataObjects, which may also help illustrate the problem.

Comment
@technicalpickles I tried to explain this issue in the IRC #jeweler channel the other evening, but thankfully luislavena has managed to state it much more coherently. In any case, we have a [workaround for DataObjects](http://github.com/datamapper/do/blob/next/do_mysql/tasks/compile.rake#L6-11), which may also help illustrate the problem.
or cancel

Please log in to comment.
74.

1 vote

Running rake install modifies the gemspec thus making the git repo dirty
0 comments Created about 1 month ago by snusnu

I wouldn't expect an action like install to change any part of the gems content. I'm aware that this is no problem at all if .gemspec is added to the .gitignore file, but there are quite some gems (including datamapper and merb) that put the gemspec into the git repo itself. I know that as a rule of thumb one shouldn't include stuff that can be generated into a repo, but still, people do it. Also, there are/were good reasons to do so, think of github gem building and wycats/bundler.

Comments

Please log in to comment.
77.

2 votes

Year is wrong in LICENSE
2 comments Created about 1 month ago by mcmire

Should be 2010 now, since it's, you know, 2010 ;) Or actually, probably should be <%= Date.today.year %> so you don't have to keep changing it.

Comments

dvyjones Sat Jan 23 04:01:57 -0800 2010 | link

It's correct in README.rdoc though...

Comment
It's correct in README.rdoc though...
or cancel

george Wed Feb 03 07:39:07 -0800 2010 | link

Here's the fix, with feature support:

http://github.com/george/jeweler/commit/52aa9742c58b8135fb063d25be7cc03876400844

Thanks for jeweler,

/g

Comment
Here's the fix, with feature support: http://github.com/george/jeweler/commit/52aa9742c58b8135fb063d25be7cc03876400844 Thanks for jeweler, /g
or cancel

Please log in to comment.
78.

0 votes

setup task to install missing dependencies
0 comments Created 23 days ago by jrun

It's nice to be able to check out a fresh project and run one command to get all dependencies. For example.

setup can be install_dependencies to align with check_dependencies

Comments

Please log in to comment.
79.

0 votes

note: git add required before rake build
1 comment Created 20 days ago by djsun

rake build (or rake gemspec) does not add files to the gemspec if they are not versioned in git. I have to do a git add . before I do rake build, otherwise my generated gemspec is not correct.

Why did I create this issue? At the very least, this is confusing and I wanted to share this with others.

To go farther, I would recommend that rake build update the gemspec even if a file isn't added to git yet. The tight coupling with git can be annoying in this case. (If you do want some sort of coupling with git, why not just check .gitignore?)

Comments

dchelimsky Tue Jan 26 06:44:03 -0800 2010 | link

+1 Please let update the manifest in the gemspec regardless of the git status. Or, if there is a moral imperative to bind 'rake build' to git, then a warning that there are uncommitted files that have not been added to the gemspec would suffice.

Comment
+1 Please let update the manifest in the gemspec regardless of the git status. Or, if there is a moral imperative to bind 'rake build' to git, then a warning that there are uncommitted files that have not been added to the gemspec would suffice.
or cancel

Please log in to comment.
80.

0 votes

Using YARD breaks due to --charset=UTF-8 option
0 comments Created 15 days ago by SFEley
Jeweler always adds the following line to the gemspec regardless of whether RDoc or YARD is selected for documentation:
```
s.rdoc_options = ["--charset=UTF-8"]
```
This throws an error from YARD when the gem is installed:
```
Installing ri documentation for etapper-0.0.5...
Building YARD (yri) index for etapper-0.0.5...
invalid option: --charset=UTF-8

Usage: yardoc [options] [source_files [- extra_files]]
(if a list of source files is omitted, lib/**/*.rb ext/**/*.c is used.)
# ...etc.
```
I've already reported this issue at the YARD repository. I believe they should keep themselves compatible with every RDoc option. However, given that they currently do not, I suggest that Jeweler should omit that line or add it to the RDoc optional generator instead of the main workflow.
Comments

Please log in to comment.

81.

0 votes

'rake gemspec:validate' always fails

0 comments Created 15 days ago by SFEley

I've seen this today in more than one of my current projects, but just to make sure it wasn't my fault, I tried it from scratch:

[12:53][~/projects]$ jeweler dummy
    create  .gitignore
    # etc.
Jeweler has prepared your gem in dummy
[12:53][~/projects]$ cd dummy

A version file has to exist before a .gemspec can be validated:

[12:53][~/projects/dummy(master)]$ rake version:write
(in /Users/steve/projects/dummy)
Updated version: 0.0.0

I try to validate the gemspec:

[12:54][~/projects/dummy(master)]$ rake gemspec:validate
(in /Users/steve/projects/dummy)
dummy.gemspec is invalid. See the backtrace for more details.
rake aborted!
undefined method `prerelease?' for nil:NilClass

(See full trace by running task with --trace)

I run the task with --trace:

[12:54][~/projects/dummy(master)]$ rake gemspec:validate --trace
(in /Users/steve/projects/dummy)
** Invoke gemspec:validate (first_time)
** Invoke version_required (first_time)
** Execute version_required
** Execute gemspec:validate
dummy.gemspec is invalid. See the backtrace for more details.
rake aborted!
undefined method `prerelease?' for nil:NilClass
/opt/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/specification.rb:1317:in `block in <class:Specification>'
dummy.gemspec:9:in `block (2 levels) in parse'
/opt/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/specification.rb:421:in `initialize'
dummy.gemspec:7:in `new'
dummy.gemspec:7:in `block in parse'
/opt/local/lib/ruby/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/gemspec_helper.rb:56:in `eval'
/opt/local/lib/ruby/gems/1.9.1/gems/jeweler-1.4.0/lib/jeweler/gemspec_helper.rb:56:in `block in parse'

I've hunted this down to a failure on assigning the version string in the "virtual" (non-file-based) gemspec that gets generated and passed to the gemspec_helper.parse method. It looks like the ValidateGemspec command class just isn't doing the same work of adding versions that the WriteGemspec command class is. (The real gemspec used to build the gem works fine.)

I don't understand the Jeweler infrastructure well enough to figure out which version addition code needs to be put in, however, or when; so I'm simply reporting the issue instead of trying to fork and fix it.

Comments

Please log in to comment.

82.

0 votes

Default rakefile names testing dependency "thoughtbot-shoulda" instead of "shoulda"
2 comments Created 11 days ago by Bastes

Apparently no gem answers to the name "thoughtbot-shoulda" anymore, so the default rakefile breaks when it comes down to testing.

Comments

Bastes Fri Jan 29 05:37:48 -0800 2010 | link

Just checked the sources and didn't find any "thoughtbot-shoulda" in, so I guess it's probably an earlier problem which fix hasn't been released in the gem yet.

Comment
Just checked the sources and didn't find any "thoughtbot-shoulda" in, so I guess it's probably an earlier problem which fix hasn't been released in the gem yet.
or cancel

technicalpickles Fri Jan 29 15:50:10 -0800 2010 | link

Do you not have gems.github.com in your sources? That's where thoughtbot-shoulda live.

As for fixes, yeah, that's pretty likely that it's been fixed and hasn't been released yet.

Comment
Do you not have gems.github.com in your sources? That's where thoughtbot-shoulda live. As for fixes, yeah, that's pretty likely that it's been fixed and hasn't been released yet.
or cancel

Please log in to comment.
83.

0 votes

adding the --local option to the install task's call to gem install would speed things up
1 comment Created 11 days ago by oxtralite

RubyGems (version 1.3.5) contacts the remote repo even when not needed. The result is that jeweler's rake install task takes longer than needed. If the install command (Jeweler::Commands::InstallGem.run) used the --local option it would avoid this and speed up local gem installs.

Comments

technicalpickles Sun Jan 31 22:21:22 -0800 2010 | link

If you look through the history of InstallGem, you'll probably see that --local has been used in the past. iirc, it was last removed because it doesn't properly resolve dependencies.

I saw you filed a bug about this against RubyGems itself. This seems like it is more properly fixed there than in Jeweler.

Comment
If you look through the history of InstallGem, you'll probably see that --local has been used in the past. iirc, it was last removed because it doesn't properly resolve dependencies. I saw you filed a bug about this against RubyGems itself. This seems like it is more properly fixed there than in Jeweler.
or cancel

Please log in to comment.
84.

0 votes

no such file to load -- spec/rake/spectask
0 comments Created 5 days ago by sMAshdot

Hi!

when building a new project with the --rspec option, the rake gemspec fails with this message:

rake aborted!
no such file to load -- spec/rake/spectask
[redacted]/rakefile:21

I followed the order of procedures of the README.
What do I need to do?

Comments

Please log in to comment.
85.

0 votes

Jeweler uses the old 'yardoc' task.
0 comments Created 5 days ago by postmodern

In YARD 0.4.0 the YARD documentation task was renamed to 'yard'.
http://github.com/lsegal/yard/commit/ad38a68dd73898b06bd5d0a1912b7d815878fae0

I have made the necessary changes in my fork of Jeweler:
http://github.com/postmodern/jeweler/tree/postmodern

Comments

Please log in to comment.
86.

0 votes

Jeweler should support creating markdown or textile formatting README files.
0 comments Created 5 days ago by postmodern

YARD supports using documentation markup other than RDoc (SimpleMarkup), such as MarkDown or Textile.

Since Jeweler already supports adding YARD to projects, it should also allow creating MarkDown or Textile formatted README files.

I've added the --markdown and --textile options to Jeweler::Generator::Options, and modified the generator to use the README.md or README.tt templates. I also made sure to specify the --markup option with YARD::Rake::YardocTask.new when using MarkDown or Textile.
http://github.com/postmodern/jeweler/commit/694f1eade0d614f7cfc52a03bb2c6b5c02b9c041

Comments

Please log in to comment.
87.

0 votes

--git-remote command line option
0 comments Created 3 days ago by jellehelsen

The command line option --git-remote does not seem to work. When I use jeweler --git-remote my.git.host:/path/to/repo the git config still points to github for the origin. It seems the command line option never makes it to the generator.
I made a simple fix available at http://github.com/jellehelsen/jeweler .

Comments

Please log in to comment.
88.

0 votes

Development dependencies are set to github gems that are unavailable
0 comments Created 2 days ago by benschwarz

mhennemeyer-output_catcher && devver-construct are not available via github gems any more and thusly the test suite cannot be run.

Comments

Please log in to comment.
89.

0 votes

Use jeweler without Git
0 comments Created 1 day ago by nbeyer

Perhaps this isn't a frequent request, but it would be nice to be able to use jeweler without Git. I installed jeweler and tried to create a new gem and it blew up because Git wasn't on the path. I couldn't even run 'jeweler --help' without Git on the path.

Once I installed Git, jeweler still complained ... i didn't have a "~/.gitconfig" file. I created that and it finally started working.

Comments

Please log in to comment.
90.

0 votes

depend on grit, rather than git
0 comments Created about 5 hours ago by xiongchiamiov

schacon's git gem is horribly outdated, and is deprecated in favor of grit. While updated forks exist, there are still many issues with any one you choose, and it makes trying to use any project that depends on git a headache.

Comments

Please log in to comment.

Labels

▾
@Josh Nichols
▾
autospec
▾
bug
▾
dependency
▾
enhancement
▾
extensions
▾
feature
▾
from-lighthouse
▾
gemcutter
▾
gemspec
▾
generator
▾
git
▾
gitconfig
▾
github
▾
java
▾
mingw
▾
rake
▾
release
▾
rspec
▾
ruby 1.9
▾
rubyforge
▾
waiting for release

technicalpickles / jeweler

Pledgie Donations

bugx The Umlaut problem: UTF-8 chars get converted to unicode entities

Comments

Comments

waiting for releasex Allow jeweler and gemspec to be agnostic (you can use rake or thor)

Comments

Comments

waiting for releasex allow for extensions

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

bug
x

The Umlaut problem: UTF-8 chars get converted to unicode entities

waiting for release
x

Allow jeweler and gemspec to be agnostic (you can use rake or thor)

waiting for release
x

allow for extensions