Every repository with this icon (
Every repository with this icon (
| Description: | Opinionated tool for creating and managing Rubygem projects edit |
-
1 comment Created 5 months ago by SoleoneThe Umlaut problem: UTF-8 chars get converted to unicode entitiesbugxWhen 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
-
3 comments Created about 1 month ago by rsanheimbugxversion bumps fail with no changes to commitgitxhey Josh
I feel like I'm missing something here, as I've used this plenty of times with out issue. But this is happening in my latest version bump attempts:
~/src/oss/runcoderun-gem (master)$ rake version:bump:minor (in /Users/rsanheim/src/oss/runcoderun-gem) Current version: 0.2.2 rake aborted! git commit '-m' 'Version bump to 0.3.0' 2>&1:# On branch master # Changed but not updated: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: version.yml # no changes added to commit (use "git add" and/or "git commit -a") (See full trace by running task with --trace) ~/src/oss/runcoderun-gem (master)$Comments
technicalpickles
Thu Oct 01 20:31:35 -0700 2009
| link
it's kinda hard to tell without a full backtrace. It's a little suspect that the file is version.yml instead of VERSION.yml. Also, what version of jeweler are you using?
Would it have a problem with a lowercase file vs uppercase?
I update pretty frequently, so I usually have the latest version of jeweler.
technicalpickles
Wed Oct 07 10:17:23 -0700 2009
| link
Yeah, I kinda suspect that'd be a problem since everywhere in the code refers to VERSION.yml. Did it get renamed at some point or something?
-
Add more rubyforge docs to prevent errors
7 comments Created about 1 month ago by grosserThings that would have helped me:
- run rake rubyfordge:setup - add a least an empty /rdoc directory mit README.rdoc - add at least and empty task :rdoc do;endComments
technicalpickles
Sun Oct 04 17:41:46 -0700 2009
| link
Can you please elaborate on the type of errors you were running into?
Not sure if it's just the formating, but I'm exactly sure of all the things you're suggesting.
rake aborted!
Don't know how to build task 'rdoc'is what i am getting when i dont have a rdoc task, and if i dont have a rdoc directory
total size is 0 speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1058) [sender=3.0.5]
rake aborted!
Command failed with status (23): [rsync -av --delete rdoc/ grosser@rubyforge...]so i needed to add rdoc task, and add an rdoc directory
atm im doing:
# fake task so that rubyforge:release works task :rdoc do
`mkdir rdoc` `echo documentation is at http://github.com/grosser/#{project_name} > rdoc/README.rdoc`end
technicalpickles
Mon Oct 05 07:53:49 -0700 2009
| link
Thanks for clarifying.
So, it probably makes more sense to not attempt to publish docs to rubyforge if you don't have a related docs task.
This is actually configurable:
Jeweler::RubyforgeTasks.new do |rubyforge| rubyforge.doc_task = :some_task endThis could be updated such a way to allow you to set it to false, or :none, or something like that, so it doesn't attempt to publish in that case.
why not do something like:
task = Rake::Task[doc_task] rescue puts('could not find #{doc_task}...') #dont crash when task is not defined task.invoke if task
technicalpickles
Mon Oct 05 08:27:44 -0700 2009
| link
I don't know, I think I'd rather have it be a little more explicit and fail until you tell it not to do anything.
-
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.
-
3 comments Created about 1 month ago by josevalimAllow jeweler and gemspec to be agnostic (you can use rake or thor)waiting for releasexThor 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.
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!
georgeguimaraes
Mon Oct 19 09:22:27 -0700 2009
| link
Ok, the comment above was done by @josevalim. ;)
-
jeweler doesn't work with the newest version of reek
4 comments Created about 1 month ago by priteauI 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.
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).
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.
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.
-
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.cI'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!
any possibility for mkrf_conf.rb love in there, as well?
Thanks!
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.
-
1 comment Created 18 days ago by cesardevelopmentjruby -S gem install -> gem will be installed in the RUBY_HOME not JRUBY_HOMEjavaxinstalling a gem with
jruby -S gem install does not work as expected.
the gem in installed, but not in the jruby gem path, rather in the ruby gem path.
also forcing sudo is not needed (and not good) for jruby gems.is there a work around for this?
Comments
technicalpickles
Wed Nov 04 07:13:17 -0800 2009
| link
I'm assuming your talking in the context of running
rake install?I haven't used jruby at all, so I'm not really sure what the deal is
I do know that jeweler itself doesn't have anything to do with RUBY_HOME, so I'd guess that's something in gem.
As for sudo, that's being taken up in a separate issue, #51.
-
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?
This is possible.
# Specify where gem executables should be copied to. # # This is an optional setting. # The default is: bin bin_path "my/executables"
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
I went with the following:
--bundlerflag to the generatoruse
./gbinfor the bundled gem pathadd both
./vendorand./gbinto .gitignore.Commits viewable on: http://github.com/jsmestad/jeweler/tree/bundler_support
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.
It makes it easy to fork a gem and just run
./bin/rake specafter doinggem 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 -
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
-
Incomplete paragraph in "Customizing your project's gem specification" wiki page
1 comment Created 16 days ago by agrimmThe 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.
-
override user.name and user.email by ENV variables
0 comments Created 3 days ago by blindgaengerAccording to
git help configyou 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
-
[PATCH] Removes reference to sudo in install task description
0 comments Created 3 days ago by snusnuThx a lot for the work on removing sudo! Here's a small patch that corrects the install task description
http://github.com/snusnu/jeweler/commits/task_description_fix
Comments
-
generators for shindo (http://github.com/geemus/shindo).
>Pull from: http://github.com/geemus/jeweler/commit/2e6aae1afd6c0994023ed06c5b3215d58cf1bab9
Thanks,
wesComments
- @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▾
- Apply to Selection
-
Change Color…
Preview:preview
- Rename…
- Delete












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.