Now I can see. Your previous link was
https://github.com/torquebox/jruby-maven-plugins/tree/master/gem-maven-plugin/
Which has a different goal in the README. The root of the project has a
different README that really does what we have discussed:
https://github.com/torquebox/jruby-maven-plugins
That was the cause of the confusion. I'll take a look at it later when I
find some time.
Thanks,
Rodrigo.
Em 27-03-2012 14:07, kristian escreveu:
just look at that example
https://github.com/torquebox/jruby-maven-plugins/tree/master/gem-maven-plugin/src/it/small-project
- Kristian
On Tue, Mar 27, 2012 at 10:35 PM, kristian<m.krist...@web.de> wrote:
On Tue, Mar 27, 2012 at 10:34 PM, Rodrigo Rosenfeld Rosas
<rr.ro...@gmail.com> wrote:
Em 27-03-2012 13:58, kristian escreveu:
On Tue, Mar 27, 2012 at 10:26 PM, Rodrigo Rosenfeld Rosas
<rr.ro...@gmail.com> wrote:
That may seem like a small project for you that already knows about all
internals for writing such project, but this is not trivial to me.
I don't even know how to make Maven resolve my gem dependencies.
you can use
https://github.com/torquebox/jruby-maven-plugins/tree/master/gem-maven-plugin/
which comes basically from me.
Sorry but I think this gem has a different purpose from what we just
discussed. I wasn't meaning to gemify a maven artifact.
I was talking about including the Ruby gem dependency inside the pom.xml.
That is how I understood that Maven would be able to manage the gems.
yes, exactly what that plugin does !!
Kristian
