On Wed, Jan 7, 2009 at 3:31 PM, Alex Coles <[email protected]> wrote: > > On Wed, Jan 7, 2009 at 6:00 PM, Luis Lavena <[email protected]> wrote: >> >> On Wed, Jan 7, 2009 at 2:56 PM, Alex Coles <[email protected]> wrote: >>> >>> On Wed, Jan 7, 2009 at 9:46 AM, Chris Van Pelt <[email protected]> wrote: >>>> >>>> I can get the gem to compile from source, but I had to remove a jar >>>> file from the Manifest and remove some java setup stuff from the >>>> Rakefile. I also changed the version.rb to 0.9.10.1 to avoid having >>>> to compile everything from source and deal with the cluster fuck of >>>> all my dependencies in my merb app. I finally just copied the gem >>>> file from my system cache directory into my merb dir and was able to >>>> thor merb:gem:redeploy... >>>> >>>> Sooo much fun :) Thanks for the help yall! >>> >>> This issue should be resolved on MRI: >>> http://github.com/sam/do/commit/0e832cf25acf4212552554cd9fce347c580ee618 >>> >> >> One of the things that rake-compiler does is avoid playing with the manifest. >> >> In that way, the extension don't need to be present in there and yet >> still, be bundled in the binaries. >> >> Perhaps similar approach could be taken for setup_java_extension? >> I remember I did it for c extension. > > Moving to rake-compiler for Java compilation is on the TODO list here: > http://www.datamapper.org/doku.php?id=jruby:todo > I am definitely in agreement -- both in principle, and increasingly in > practice -- that this is the way to go! > > Playing with the Manifest broke things for MRI users last night. I've > made a few commits this afternoon to try to get things working again > on both MRI and JRuby, but more extensive debugging of what's going in > the compilation/packaging workflow.
Is really tricky to find the spot where things go hairy in the rakefiles. Is something I had dealt with several projects and I do several mistakes lot of times on that subject :-P > As of right now, if you're running on JRuby, there is a caveat: you'll > have to manually do a jruby -S rake compile, before executing the > jruby -S rake gem task. > > (rant) > IMO Hoe doesn't help make things clear or understandable! It just adds > one additional layer of complexity, without a huge amount of benefit > (although admittedly, I'm not the one pushing the gems to RubyForge). > (/rant over) I got rid of that in rake-compiler itself: http://github.com/luislavena/rake-compiler/tree/master/tasks/release.rake It uploads the packaged files specific to the version and generates the changelog and notes from the History file. So far, it worked: http://rubyforge.org/frs/shownotes.php?release_id=29081 >From the todo: # refactor Rakefiles * refactor various mess of conditional "if JRUBY" statements * 'jruby -S rake gem' should automatically compile Java extension If doing rake-compiler way, you could have: "rake java gem" that generates both pure ruby and java gems at the same time. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
