drbrain at segment7.net
Thu Jan 31 17:23:26 EST 2008
Oops, I only sent this to Trans.
On Jan 30, 2008, at 13:10 PM, Trans wrote:
> On Jan 30, 12:48 pm, "Luis Lavena" <luislav... at gmail.com> wrote:
>> On Jan 30, 2008 3:43 PM, Trans <transf... at gmail.com> wrote:
>>> Why is Rubygems now issuing warnings when building, eg.
>>> WARNING: no rubyforge_project specified
>>> WARNING: RDoc will not be generated (has_rdoc == false)
>>> I've never seen it do this before. How to I silence it? (Using ruby,
>>> not command line).
>> These warnings where introduced due bad gem specifications.
>> Setting the correct values in the gem specification will silent
>> these warnings.
> That's not so. The has_rdoc is set to false for a reason.
Then you're a bad person. Not generating RDoc/ri is hostile to your
> Plus one might not have a rubyforge project.
There's an "orphans" project on rubyforge for gems that are lacking a
real project. If you're building an internal gem, I think you can
deal with it.
More information about the Rubygems-developers