Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Files in axiom-types and descendants_tracker gems use 400 and 440 modes #1989
may I ask where exactly the problem lies ?
yes, jruby-complete.jar does not contain those. jar-dependencies will install those gem on the fly when needed. the idea was to minimize the "download" when you first use jar-dependencies since even with ruby-maven already installed it will first download the half the internet. the second run is fast since the download is cached in the local maven repository.
the above gems are used for a pure ruby version of maven-model - let me see if jar-dependencies will work without those.
This isn't about jruby-complete.jar or using jar-dependencies. It's the simple fact that release tarballs should not contain files that are not group and world readable. Really, this should be fixed upstream, but since upstream is ignoring the issue, JRuby should work around this.
I only noticed the problem because I'm the JRuby port maintainer for OpenBSD, and the OpenBSD porting tools complain if you try to create a package that contains files that aren't group and world readable.