Warbler and gemspec

Hello,

I am using jruby 1.5.6, rack 1.0.7, and warbler 1.2.1.

I am using warble to create a war file. The war file does not contain
all the gem files needed to run the site. I think this occurs because
the gemspec in the specifications folder when “gem install” is run does
not specify all the necessary files in the s.files entry.

The gemspec in the specifications folder is different than the gemspec
for the respective gem in github. I suspect that if the gemspec from the
github gem is the same as gemspec in the specifications folder, the war
file will generate correctly.

Does anyone have any insight on why the gemspec is different than the
gem github gemspec?

Thanks,
Yin

On Thu, Mar 10, 2011 at 8:54 AM, Yin A. [email protected] wrote:

for the respective gem in github. I suspect that if the gemspec from the
github gem is the same as gemspec in the specifications folder, the war
file will generate correctly.

Does anyone have any insight on why the gemspec is different than the
gem github gemspec?

Which gem is giving you issues? Gemspecs are created when the gem is
packaged, before it is uploaded to rubygems.org. If a particular
gemspec is causing problems your best bet is to build a new version of
it yourself and install it locally.

/Nick

With help from Nick at #jruby and Wayne at #rvm, determined that the
problem resides with rubygems. I was using rubygems 1.6.1. When I
downgrade to rubygems 1.4.2 with “gem update --system 1.4.2”, problem
solved. Gemspec is generated correctly.

The correct gemspec includes a fully specified s.files. This list of
files is used by warble to include support files in the war.
Subsequently, the war generates correctly with command “warble”.

Thanks.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs