Hi, On Tue, Mar 9, 2010 at 1:00 AM, Charles Oliver Nutter <head...@headius.com> wrote: >>> * Native launcher...is it ready to go? >> >> Ready to go. We're continuing to make tweaks, but those can be picked >> up separately via gem install. We should also move the launcher to >> 1.0. > > Awesome. I realized today I haven't been running with the native > launcher, so I'm installing it now and will use it exclusively. But I > assume others have been using it without issue anyway.
Yeah, it looks like we are ready for 1.0 version. I felt a bit guilty lately when we were fixing the launcher bugs but reused the same 0.9.9 version :) In theory, we should be bumping the version after fixes and before integration with jruby repo. > What's the plan for release? I assume we'll just ship the bash script > and recommend people install the gem to get the native launcher? Do we > have builds prepared for specific platforms? Include a pre-built one > with the OS X installer? > > Gem install seems totally ok to me, to be honest. That's where things are a bit unclear to me. We can't have a generic JRuby package that would work on all platforms, since the launcher needs to be built on particular platform. So, either we need to have multiple install bundles for all platforms (with launchers pre-built) or to continue with the generic bundle and ask users to use gem install. On the other hand, it would be nice to have platform-specific bundles for at least the most common platforms. Our generic bundle already contains Windows native launcher prebuilt, so Windows is covered. If we are to have MacOS installer, it would be nice to have the launcher prebuilt and included in there. And the only major platform left is Linux. I think Wayne had some thoughts on how to build the launcher so that it would be compatible with as much Linux distros as possible (by carefully selecting the toolchain and compiler/lib versions). Personally, I think that having prebuilt bundles for Windows/MacOS/Linux would be more than enough. Thanks, --Vladimir P.S. One thing that worries me is that currently we force the native launcher to be built during our builds, but on platforms where launcher is not yet supported or where folks just don't have the compiler, that would mean that previously working jruby build would start failing. Maybe there should be some smarts in our build to turn the launcher build/install off? >>> * ant/rake integration...anything left to be done? >> >> Nothing major on my list. There are still some weird bugs -- for >> example when converting JRuby's build.xml to .rb and trying to run a >> compile, I get a SEGV. Even though there's a converter class there, we >> probably shouldn't advertise using pure-Ruby Ant projects until some >> of that stuff is ironed out. > > If you can show me the dump information I might be able to find a > reason for it. I suspect it's not directly related to the ant/rake > stuff and is a bug elsewhere in JRuby or our native bits... > > Perhaps we should try to repurpose Tom's blog post as a new set of > wiki pages on this new integration? We obviously should have > something... > >>> * Quick pass over recently-updated and recently-added bugs to see if >>> there's any easy ones we can drop in > > I went through a handful and will continue on that path this evening. > >>> * Rails 3 support: I know it's working, because some folks are playing >>> with it...but are there things we should fix? Where do we stand on >>> test cases? >> >> I'll be working on Rails 3 stuff this week and you'll hear from me if >> there's anything serious. > > Excellent. > > - 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
