hello, started to write a maven gem plugin a while ago and started to use it in two of my projects.
http://github.com/mkristian/jruby-maven-plugins/ it introduce a gem maven artifact, i.e. you can manage your gems with maven. with maven3 you can declare gemcuttter to be a maven repository (with a custom layout) and maven downloads the gems from there and installs them in the local repository (this is not possible with maven2 as far I know). the generated pom is minimal without any dependencies - it is possible to parse the gemspec and create a much better pom (coming soon). after installing the gem in local repository, the maven plugin takes all the gems (declared as dependencies) and installs them the ruby way (i.e. jgem install -l xyz.gem). to have clean environment you can set to system properties: jruby.gem.home and jruby.gem.path to target/rubygems and have a per project rubygems repository. there are some more goals to the plugin, like package a gem from gemspec or from a pom. gem from a pom can be a ruby only gem or one with a java extension which uses maven packaging 'java-gem'. some more ideas you get through the integration tests (maven3 + maven2) - see the flags.txt for the commandline arguments, goals.txt for goals executed with the test. jruby-maven-plugins/gem-maven-plugin/src/it and for maven3 only there is modular setup (needs some tests to see whether things are done right or not): $ cd jruby-maven-plugins/gem-maven-plugin/play $ mvn3 clean install example of a project with a java-gem: http://github.com/mkristian/dm-lucene-adapter example of rails project with gem artifacts: http://github.com/mkristian/sahyadri so please comment on these ideas. with regards Kristian with regards Kristian --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
