did look at the complete distribution and used pack200 to reduce the jars which leads to:

$ ll -h *zip
41M  jruby-dist-9.0.0.0-SNAPSHOT-bin.zip
13M  jruby-dist-9.0.0.0-SNAPSHOT-src.zip
18M  jruby-dist-9.0.0.0-SNAPSHOT-pack200.zip

to use the pack200.zip you need to run a "post_install" script

find -name "*pack200.gz" | sed "s/\(.*\).pack200.gz/\1.pack200.gz \1.jar/" | xargs -L1 unpack200 -r

the reduction in size is impressive and worth for using with rbenv, rvm and alike. maybe even windows installer. the post_installer could be also an executable jar.

another point are the native libraries

• both lib/jruby.jar has bundled the jni/* directory inside the jar and the dist archive contains lib/jni/* as well

I believe windows installer does use pack200 internally as part of install4j.

did some pack200 stuff on https://github.com/jruby/jruby/tree/pack20

jruby-dist-bin.tar.gz 37MB
jruby-dist-bin.zip 38MB
jruby-dist-bin200.tar.gz 17MB
jruby-dist-bin200.zip 18MB
jruby-dist-src.tar.gz 8MB
jruby-dist-src.zip 13MB

after unzipping jruby-dist-bin200.* archives you need to run bin/unpack200.sh
which takes a couple of seconds. did not yet tried for a windows unpack200.bat - first I need to know whether this is OK to go this route !

I personally would go for the bin200 archives - the reduction is really impressive and makes a difference in installing jruby (for me).

I also started to repack ruby-maven and ruby-maven-libs so they can be installed a default gems and refactored the script for installing default gems from lib/pom.rb into its own ruby file (need to reuse it for maven/jruby-dist) but this is still work in process.

I also added some length test in test/check_versions.sh which runs with travis to avoid the unwanted explosion of archive size we did see with jruby-9.0.0.0.pre1

I also added some length test in test/check_versions.sh which runs with travis to avoid the unwanted explosion of archive size we did see with jruby-9.0.0.0.pre1

That's a really good idea.

Very nice @mkristian, and I agree the size reduction is significant. Only thing that gives me pause is releasing too many distribution archives since I feel like we'd need to still provide the unpacked versions too.

What do you think @enebo?

The original problem was dist was too big and the answer is to continue disting the big file and add more dist files to the release? I don't think this is actually solving a problem. I also don't think most users know what pack200 is and so they won't download it because they won't think they can unpack it. pack200, to me, fits better into installers since it can be hidden from the person installing.

I always feel like the dissenting voice :) We release waaay too many files already. In another couple of years I will be uploading 1GB of diced permutations of our bits (let us not forget we are not even doing truffle dists yet).

@mkristian Yes, cherry-pick any size improvements other than pack200 stuff to master. Perhaps some day we'll explore pack200 distribution.

@headius the explosion of the size of most distribution artifacts for 9.0.0.0.pre1 came through the embedded jruby-complete-1.7.19 inside the jruby-readline setup. this I fixed a while ago when I released jruby-readline-1.0.gem to maven central.

beside this there are quite a few place to reduce amount of maven modules and attached artifacts but that is not part of the pack200 branch.

so I reworked the artifacts which gets "deployed" to maven central:

• two less maven modules:
  • maven/jruby-noasm is gone
  • maven/jruby-stdlib is part of lib/
• three less deployed artifacts:
  • jruby-noasm.jar
  • jruby-core-noasm.jar which is the jruby-core.jar now
  • jruby-core-complete.jar is gone

the jruby-core pom uses the dependency-reduced pom after shading asm and jnr-jffi (which uses asm).

this change reduced the upload on release about 20MB.

finally I added jruby-dist-bin200.tar.gz which is 17MB. here I also replaced the bin/jruby script with one which unpacks all the jars when used the first time before executing the jruby. any further bin/jruby execution works as usual - on linux ONLY or when there is a bash.

so overall it is a reduction of attached artifacts and total upload size :)

see more details on pack200 branch.

once maven-3.3.0 is released I will work on the ruby-maven-libs.gem and reduce the dist size even more.

just a follow up:

with the new ruby-maven and ruby-maven-libs gem it is finally possible to install those gems as default gems inside the jruby-dist files which will reduce the size by at least 8MB

@mkristian are these new versions on master now as default gems? Can this be closed now?

@enebo the new versions are on master but not as default gems. give me the
weekend to finalize it. had already done something but those scripts are on
my old laptop which is not with me right now.

On Fri, Jun 26, 2015 at 5:34 PM, Thomas E Enebo notifications@github.com
wrote:

@mkristian https://github.com/mkristian are these new versions on
master now as default gems? Can this be closed now?

—
Reply to this email directly or view it on GitHub
#2487 (comment).

@mkristian okie dokie...just checking

done on both branches