|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
1.1.3 Warbler rake gem errorSmall problem getting Warbler .9.9 running with JRuby 1.1.3:
Easy enough work around. I just re-installed rake on top of the one that comes with the distro. I moved to 1.1.3 from 1.1.1 which had the gem in the cache directory as part of the jruby 1.1.1 distro. My output: mike@mike-laptop:~/projects/ut-nedss$ jruby -S warble war:clean mike@mike-laptop:~/projects/ut-nedss$ jruby -S warble war rake aborted! Cannot load gem at [/home/mike/opt/jruby-1.1.3/lib/ruby/gems/1.8/cache/rake-0.8.1.gem] in /home/mike/projects/ut-nedss /home/mike/opt/jruby-1.1.3/lib/ruby/site_ruby/1.8/rubygems/format.rb:41:in `from_file_by_path' (See full trace by running task with --trace) mike@mike-laptop:~/projects/ut-nedss$ jruby -S gem install rake -v=0.8.1 Successfully installed rake-0.8.1 1 gem installed Installing ri documentation for rake-0.8.1... Installing RDoc documentation for rake-0.8.1... mike@mike-laptop:~/projects/ut-nedss$ jruby -S warble war jar cf nedss.war -C tmp/war . -- Mike Herrick Program Manager, Collaborative Software Initiative mike@... http://www.csinitiative.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: 1.1.3 Warbler rake gem errorMike Herrick wrote:
> Small problem getting Warbler .9.9 running with JRuby 1.1.3: > > Easy enough work around. I just re-installed rake on top of the one that > comes with the distro. > > I moved to 1.1.3 from 1.1.1 which had the gem in the cache directory as > part of the jruby 1.1.1 distro. Oh, rats. We thought it would be fine to not ship the gems in the cache, but I didn't think of Warbler using them to include in the WAR file. This is something we could easily respin the release archive to include...do you think we should? I think this will affect a lot of people. - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: 1.1.3 Warbler rake gem errorThat or maybe Warbler could fix it up somehow.
Pretty easy work around, but yeah - everyone basically uses Warbler now so it will happen a lot and might scare the brand-newbs. Mike Charles Oliver Nutter wrote: > Mike Herrick wrote: >> Small problem getting Warbler .9.9 running with JRuby 1.1.3: >> >> Easy enough work around. I just re-installed rake on top of the one >> that comes with the distro. >> >> I moved to 1.1.3 from 1.1.1 which had the gem in the cache directory >> as part of the jruby 1.1.1 distro. > > Oh, rats. We thought it would be fine to not ship the gems in the cache, > but I didn't think of Warbler using them to include in the WAR file. > This is something we could easily respin the release archive to > include...do you think we should? I think this will affect a lot of people. > > - Charlie > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: 1.1.3 Warbler rake gem errorMike Herrick wrote:
> That or maybe Warbler could fix it up somehow. > > Pretty easy work around, but yeah - everyone basically uses Warbler now > so it will happen a lot and might scare the brand-newbs. I think I'm going to make an executive decision and push out a new bin dist that includes the gem files. It's going to mess up too many people. - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: 1.1.3 Warbler rake gem errorCharles Oliver Nutter wrote:
> Mike Herrick wrote: >> That or maybe Warbler could fix it up somehow. >> >> Pretty easy work around, but yeah - everyone basically uses Warbler >> now so it will happen a lot and might scare the brand-newbs. > > I think I'm going to make an executive decision and push out a new bin > dist that includes the gem files. It's going to mess up too many people. I've pushed new dists to the server for this. Since it's still the weekend, I think we're ok just replacing what's there. I've also updated the 1_1_3 tag and trunk. Mike: Can you grab it and confirm it's working? All: Because we only have so many hands here, perhaps we should plan on always doing a release of the dists a day or two before we announce it, so those of you trying things out can test it before we tell the world? Or we push out an RC each time before the main release? Obviously we'd like to avoid this dist-juggling every time. - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: 1.1.3 Warbler rake gem errorSure thing will try now.
BTW, I did successfully run our app with 1.1.3 (i.e., stuck jruby 1.1.3 complete in the .war). Mike Mike Herrick Program Manager, Collaborative Software Initiative mike@... http://www.csinitiative.com Charles Oliver Nutter wrote: > Charles Oliver Nutter wrote: >> Mike Herrick wrote: >>> That or maybe Warbler could fix it up somehow. >>> >>> Pretty easy work around, but yeah - everyone basically uses Warbler >>> now so it will happen a lot and might scare the brand-newbs. >> >> I think I'm going to make an executive decision and push out a new bin >> dist that includes the gem files. It's going to mess up too many people. > > I've pushed new dists to the server for this. Since it's still the > weekend, I think we're ok just replacing what's there. I've also updated > the 1_1_3 tag and trunk. > > Mike: Can you grab it and confirm it's working? > > All: Because we only have so many hands here, perhaps we should plan on > always doing a release of the dists a day or two before we announce it, > so those of you trying things out can test it before we tell the world? > Or we push out an RC each time before the main release? Obviously we'd > like to avoid this dist-juggling every time. > > - Charlie > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: 1.1.3 Warbler rake gem errorGreat news Mike, thanks. So far no major crap-ups with this release,
though we've had a couple scares. Mike Herrick wrote: > Sure thing will try now. > > BTW, I did successfully run our app with 1.1.3 (i.e., stuck jruby 1.1.3 > complete in the .war). > > Mike > > Mike Herrick > Program Manager, Collaborative Software Initiative > mike@... > http://www.csinitiative.com > > > Charles Oliver Nutter wrote: >> Charles Oliver Nutter wrote: >>> Mike Herrick wrote: >>>> That or maybe Warbler could fix it up somehow. >>>> >>>> Pretty easy work around, but yeah - everyone basically uses Warbler >>>> now so it will happen a lot and might scare the brand-newbs. >>> >>> I think I'm going to make an executive decision and push out a new >>> bin dist that includes the gem files. It's going to mess up too many >>> people. >> >> I've pushed new dists to the server for this. Since it's still the >> weekend, I think we're ok just replacing what's there. I've also >> updated the 1_1_3 tag and trunk. >> >> Mike: Can you grab it and confirm it's working? >> >> All: Because we only have so many hands here, perhaps we should plan >> on always doing a release of the dists a day or two before we announce >> it, so those of you trying things out can test it before we tell the >> world? Or we push out an RC each time before the main release? >> Obviously we'd like to avoid this dist-juggling every time. >> >> - Charlie >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: 1.1.3 Warbler rake gem errorYeah so I must have been behind a proxy at OSCON. I downloaded the
latest from http://dist.codehaus.org/jruby/ and it does indeed have: lib/ruby/gems/1.8/cache/rake-0.8.1.gem Other than that, I successfully upgraded our app to 1.1.3 I'm upgrading our build server now - that's always an interesting stat - I'll let you know if there is a notable difference in what our builds are taking with 1.1.3 vs. 1.1.1. Mike Herrick Program Manager, Collaborative Software Initiative mike@... Portland, Or 97258 http://www.csinitiative.com Charles Oliver Nutter wrote: > Great news Mike, thanks. So far no major crap-ups with this release, > though we've had a couple scares. > > Mike Herrick wrote: >> Sure thing will try now. >> >> BTW, I did successfully run our app with 1.1.3 (i.e., stuck jruby >> 1.1.3 complete in the .war). >> >> Mike >> >> Mike Herrick >> Program Manager, Collaborative Software Initiative >> mike@... >> http://www.csinitiative.com >> >> >> Charles Oliver Nutter wrote: >>> Charles Oliver Nutter wrote: >>>> Mike Herrick wrote: >>>>> That or maybe Warbler could fix it up somehow. >>>>> >>>>> Pretty easy work around, but yeah - everyone basically uses Warbler >>>>> now so it will happen a lot and might scare the brand-newbs. >>>> >>>> I think I'm going to make an executive decision and push out a new >>>> bin dist that includes the gem files. It's going to mess up too many >>>> people. >>> >>> I've pushed new dists to the server for this. Since it's still the >>> weekend, I think we're ok just replacing what's there. I've also >>> updated the 1_1_3 tag and trunk. >>> >>> Mike: Can you grab it and confirm it's working? >>> >>> All: Because we only have so many hands here, perhaps we should plan >>> on always doing a release of the dists a day or two before we >>> announce it, so those of you trying things out can test it before we >>> tell the world? Or we push out an RC each time before the main >>> release? Obviously we'd like to avoid this dist-juggling every time. >>> >>> - Charlie >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free Forum Powered by Nabble | Forum Help |