Discussion:
[jruby-dev] New JRuby Dist questions
(too old to reply)
Thomas E Enebo
2013-09-16 21:41:29 UTC
Permalink
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.enebo-***@public.gmane.org
christian
2013-09-17 09:20:54 UTC
Permalink
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
Post by Thomas E Enebo
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
Charles Oliver Nutter
2013-09-17 12:42:57 UTC
Permalink
krypt should become a "default gem" for both 1.8 and 1.9 modes. I just
haven't done it yet. Ideally all gems that are vendored by us should
be listed as default gems. If it's possible, getting them as maven
dependencies would be even better.

christian: I'm not sure if there's a better way for us to handle the
new RG 2.1 default gem support. All it does is install a
specification, bin/ stubs, and the gem's actual bin/ contents. The
rest is assumed to be in stdlib...so the "default" gem basically acts
like a hollowed-out gem.

I added support in RG 2.1 for installing all the default gem bits, but
did not go so far as to make it install the stdlib bits (since
different impls will put those in different places, it seemed like a
bigger job).

I'd love to see our initial bootstrap build eventually pull in all
vendored libraries from their actual sources. That would include:

* rake
* rdoc
* json
* psych (eventually...no -java version released yet)
* krypt
* and possibly others

Note that we're trying to stabilize for 1.7.5, so we should probably
just do what's necessary to release right now.

- Charlie
Post by christian
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]
[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
Post by Thomas E Enebo
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
christian
2013-09-19 13:47:56 UTC
Permalink
after the release of 1.7.5 I can look into how to get all those gems pulled
in via maven as long the 'actual source' is the publish gem from rubygem.org

-christian


On Tue, Sep 17, 2013 at 1:42 PM, Charles Oliver Nutter
Post by Charles Oliver Nutter
krypt should become a "default gem" for both 1.8 and 1.9 modes. I just
haven't done it yet. Ideally all gems that are vendored by us should
be listed as default gems. If it's possible, getting them as maven
dependencies would be even better.
christian: I'm not sure if there's a better way for us to handle the
new RG 2.1 default gem support. All it does is install a
specification, bin/ stubs, and the gem's actual bin/ contents. The
rest is assumed to be in stdlib...so the "default" gem basically acts
like a hollowed-out gem.
I added support in RG 2.1 for installing all the default gem bits, but
did not go so far as to make it install the stdlib bits (since
different impls will put those in different places, it seemed like a
bigger job).
I'd love to see our initial bootstrap build eventually pull in all
* rake
* rdoc
* json
* psych (eventually...no -java version released yet)
* krypt
* and possibly others
Note that we're trying to stabilize for 1.7.5, so we should probably
just do what's necessary to release right now.
- Charlie
Post by christian
I am all for consistency and there is at least one other gem vernderoed
in
Post by christian
lib/ruby/shared/ - the bouncy-castle-java gem.
of course I wonder how those krypt jar files come into existence ;)
$ mvn validate -Pdist
[INFO]
[INFO] JRuby ............................................. SUCCESS
[0.001s]
Post by christian
[INFO] JRuby Core ........................................ SUCCESS
[0.000s]
Post by christian
[INFO] JRuby Ext ......................................... SUCCESS
[0.001s]
Post by christian
[INFO] JRuby OpenSSL ..................................... SUCCESS
[0.000s]
Post by christian
[INFO] JRuby Readline .................................... SUCCESS
[0.000s]
Post by christian
[INFO] JRuby Ripper ...................................... SUCCESS
[0.001s]
Post by christian
[INFO] JRuby Integration Tests ........................... SUCCESS
[0.000s]
Post by christian
[INFO] JRuby Artifacts ................................... SUCCESS
[0.000s]
Post by christian
[INFO] JRuby Stdlib ...................................... SUCCESS
[0.001s]
Post by christian
[INFO] JRuby Dist ........................................ SUCCESS
[0.000s]
Post by christian
so openssl is part of a clean dist or did you mean that the dist profile
should create the gem along side ?
- christian
Post by Thomas E Enebo
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
Post by christian
Post by Thomas E Enebo
jruby-openssl files is in lib/ruby/shared which also could make sense
but
Post by christian
Post by Thomas E Enebo
seeing how readline puts jline in its own direction. Should we make
these
Post by christian
Post by Thomas E Enebo
packaged consistently?
-Tom
--
blog: http://blog.enebo.com twitter: tom_enebo
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
Loading...