JRuby

Make regular distro/build create the all-in-one jar by default

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: JRuby 0.9.9, JRuby 1.0.0RC1, JRuby 1.0.0RC2
  • Fix Version/s: JRuby 1.1b1
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

There has been lots of discussion on this issue, enough so that we should probably make the following change for 1.0:

  • jruby-complete.jar => jruby.jar
  • current jruby.jar => jruby-core.jar

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Charles Oliver Nutter added a comment -

Punting to post-RC2. Nick, you could probably make this work with only a bit of effort, if we all decide it should happen.

Show
Charles Oliver Nutter added a comment - Punting to post-RC2. Nick, you could probably make this work with only a bit of effort, if we all decide it should happen.
Hide
Permalink
Charles Oliver Nutter added a comment -

I'm still of the opinion that a slim jar with an appropriate manifest is plenty. I think we should punt this bug or eliminate it completely.

Show
Charles Oliver Nutter added a comment - I'm still of the opinion that a slim jar with an appropriate manifest is plenty. I think we should punt this bug or eliminate it completely.
Hide
Permalink
Charles Oliver Nutter added a comment -

Post 1.0. People can use the complete jar or rely on the manifested normal jar.

Show
Charles Oliver Nutter added a comment - Post 1.0. People can use the complete jar or rely on the manifested normal jar.
Hide
Permalink
Charles Oliver Nutter added a comment -

We need to revisit this issue especially in light of the new compiler. Fix or wontfix by 1.1

Show
Charles Oliver Nutter added a comment - We need to revisit this issue especially in light of the new compiler. Fix or wontfix by 1.1
Hide
Permalink
Charles Oliver Nutter added a comment -

Here's the new proposal that I tend to like a lot: Just put all required jars in the jruby.jar file, but not stdlib. Only jruby-complete would contain the stdlib. This is also pretty well in line with how other distributions in similar situations work...xruby provides a compilete jar, rubinius provides a largely-complete executable.

I think we can and should do that for 1.1 and leave jruby-complete to just contain the additional stdlib files.

Show
Charles Oliver Nutter added a comment - Here's the new proposal that I tend to like a lot: Just put all required jars in the jruby.jar file, but not stdlib. Only jruby-complete would contain the stdlib. This is also pretty well in line with how other distributions in similar situations work...xruby provides a compilete jar, rubinius provides a largely-complete executable. I think we can and should do that for 1.1 and leave jruby-complete to just contain the additional stdlib files.
Hide
Permalink
Charles Oliver Nutter added a comment -

I resolved this with the compromise arrangement: all jars used by JRuby at runtime now get JarJar'ed into the jruby.jar file and not included in the distribution. This allows jruby.jar to be standalone executable without the additional size and overhead of the entire standard library.

Show
Charles Oliver Nutter added a comment - I resolved this with the compromise arrangement: all jars used by JRuby at runtime now get JarJar'ed into the jruby.jar file and not included in the distribution. This allows jruby.jar to be standalone executable without the additional size and overhead of the entire standard library.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.