I am aware of https://github.com/jruby/jruby/issues/1210 https://github.com/jruby/jruby/issues/1207
which is something I am going to address with the work around the defaults gems. is there more to it ? - christian On Thu, Dec 26, 2013 at 3:44 PM, Vít Ondruch <v.ondr...@gmail.com> wrote: > Dne 23.12.2013 11:02, christian napsal(a): > > hi, >> >> since the maven build does more or less its job now, it is time to ask if >> there is something which is really annoying or something which got dropped >> during the whole migration. >> >> please speak out and let me know. for a start I add my wish-list now >> >> * get rid of build.xml ;) >> * lib/jruby.jar and the jruby-core-complete artifact are identical - >> needs to be build only ONCE >> * each of ext/* should look like usual gem project and jruby should >> utilize those gems to setup the resp. parts in lib/ruby/** >> * default gems should be cherry-picked (bin-stubs and specifications) >> from downloaded gems - I got stuck here with jruby-maven-plugin can not >> handle gems with platform **universal-java** like in krypt-core. >> * use ruby-maven (gem) where I can easily embed ruby scripts inside the >> pom.rb or Mavenfile. it also makes it easy to setup a gem project with >> jar-extension and still use `rake build` to build the gem or to `rake >> junit` to run junit tests on the java part. it also generates a pom.xml >> which works with proper maven. >> >> please comment and ADD to the list whatever you have on your mind !!! >> >> best regards, >> christian >> > > Only one issue ... bundling/repacking ... this makes JRuby unpackagable on > Fedora :/ > > > Vít > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
