hello, after reading through the maven_gem code which was commited a few days ago and having almost the same code for the gem artifact I am working on. I decided to setup a maven plugin which does take a pom and converts it into a gem.
right now you need to build the plugins from source http://github.com/mkristian/jruby-maven-plugins just install the plugins with $ mvn install -Dmaven.test.skip=true (there are two failing tests with some failures on gem index of gem.rubyforge.org) then have a look at the integration test of the gemify goal: $ cd gem-maven-plugin $ mvn integration-test $ cd src/it/gemify and look at the target directory. it gemifies the pom itself and its dependencies. the biggest advantage is that the pom.xml can use properties defining artifactIds or inherit the version,groupId from parent pom, maven builds the object model from the given pom.xml. since maven does the dependency resolution as well the pom can use pom dependencies to share common sets of "real" dependencies. one feature I will include today will be that you can call the goal with artifactId, groupId and version and then does the same procedure. one part of the code if from maven_gem and the other is shared with gem-artifact code. I have to say that maven plugins which are not included in the central repository are a bit nasty to install and call from the command line. usability improves significantly when putting a plugin onto the central repository. with regards Kristian --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
