so the gemify-maven-plugin is kind of ready:
relocations of artifact work that the relocated artifact will be used
exclusion of dependent artifact work in the sense that when
requiring the maven artifact then the same jar will be added to the
jruby classloader as maven would do when building the classloader for
that specific artifact
the dependency hull is big enough for rubygem to be complete (it can
be bigger then what maven uses because of the exclusion which are
filtered on require and some little issue.
so things work OK for me unless there are version conflicts which
rubygems can not resolve and maven can - these things do exists.
On Tue, Aug 10, 2010 at 1:40 AM, kristian [email protected] wrote:
version ~> 1.5.15 (<- that the one maven picks)
development-dependency. this can be fixed.
On Sun, Aug 8, 2010 at 2:20 AM, kristian [email protected] wrote:
now you use the command ‘maven’ instead of ‘mvn’. startup feels even
On Fri, Aug 6, 2010 at 2:05 PM, kristian [email protected] wrote:
- Standard Maven libraries (like the actual Maven libraries) would be
mostly-Ruby portion in its own gem).
Â Â http://xircles.codehaus.org/manage_email
Kristian Meier + Saumya Sharma + Sanuka Meier
Edayanmula West PO - 689532,
Pathanamthitta District, Kerala, INDIA
tel: +91 468 2319577
protect your privacy while searching the net: www.ixquick.com
Â Â Â Â Â Â Â =
Â Â Â Â Â Â q(--)p
Â Â Â Â Â Â ') (`
Â Â Â Â Â Â //Â
Â Â Â Â Â _(<Â Â / )
Â Â Â (__|/__)
To unsubscribe from this list, please visit: