I am all for consistency and there is at least one other gem vernderoed in lib/ruby/shared/ - the bouncy-castle-java gem.
of course I wonder how those krypt jar files come into existence ;) $ mvn validate -Pdist [INFO] Reactor Summary: [INFO] [INFO] JRuby ............................................. SUCCESS [0.001s] [INFO] JRuby Core ........................................ SUCCESS [0.000s] [INFO] JRuby Ext ......................................... SUCCESS [0.001s] [INFO] JRuby OpenSSL ..................................... SUCCESS [0.000s] [INFO] JRuby Readline .................................... SUCCESS [0.000s] [INFO] JRuby Ripper ...................................... SUCCESS [0.001s] [INFO] JRuby Integration Tests ........................... SUCCESS [0.000s] [INFO] JRuby Artifacts ................................... SUCCESS [0.000s] [INFO] JRuby Stdlib ...................................... SUCCESS [0.001s] [INFO] JRuby Dist ........................................ SUCCESS [0.000s] so openssl is part of a clean dist or did you mean that the dist profile should create the gem along side ? - christian On Mon, Sep 16, 2013 at 10:41 PM, Thomas E Enebo <tom.en...@gmail.com>wrote: > I thought we were able to ship jruby-openssl now? I think dist defaults > to not creating this as part of dist. > > I notice that jline is in lib/ruby/shared/readline which makes sense. All > jruby-openssl files is in lib/ruby/shared which also could make sense but > seeing how readline puts jline in its own direction. Should we make these > packaged consistently? > > -Tom > > -- > blog: http://blog.enebo.com twitter: tom_enebo > mail: tom.en...@gmail.com >
