-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Remove duplicate gems when producting logstash artifacts #18340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 3 commits
f474d49
2daa98c
874851d
1756426
527b84f
336135a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -279,7 +279,11 @@ tasks.register("installCustomJRuby", Copy) { | |
| dependsOn buildCustomJRuby | ||
| description = "Install custom built JRuby in the vendor directory" | ||
| inputs.file(customJRubyTar) | ||
| outputs.dir("${projectDir}/vendor/jruby") | ||
| // Don't re-extract if core JRuby is already installed. This works around | ||
| // gem deduplication when rake calls back in to gradle. | ||
| onlyIf { | ||
| !file("${projectDir}/vendor/jruby/bin/jruby").exists() | ||
| } | ||
| from tarTree(customJRubyTar == "" ? jrubyTarPath : customJRubyTar) | ||
| eachFile { f -> | ||
| f.path = f.path.replaceFirst("^jruby-${customJRubyVersion}", '') | ||
|
|
@@ -294,7 +298,11 @@ tasks.register("downloadAndInstallJRuby", Copy) { | |
| dependsOn=[verifyFile, installCustomJRuby] | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. COREREVIEW: why is there a dep on |
||
| description = "Install JRuby in the vendor directory" | ||
| inputs.file(jrubyTarPath) | ||
| outputs.dir("${projectDir}/vendor/jruby") | ||
| // Don't re-extract if core JRuby is already installed. This works around | ||
| // gem deduplication when rake calls back in to gradle. | ||
| onlyIf { | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In the interplay between gradle/rake it is hard (IMO impossible) to define a sane dependency graph to ensure that gems are cleaned after jruby has been installed and bundler has been run. TO get around issues where gradle was being tricked in to thinking we need a fresh jruby install when gems have been cleaned up, only install jruby when the executable is not in the expected place. This is kind of a hack as i could see a workflow where this would cause an issue with an unexpectedly old or broken jruby but I cant think of a way around it without majorly refactoring how our gradle/rake tasks are organized. |
||
| !file("${projectDir}/vendor/jruby/bin/jruby").exists() | ||
| } | ||
| from tarTree(downloadJRuby.dest) | ||
| eachFile { f -> | ||
| f.path = f.path.replaceFirst("^jruby-${jRubyVersion}", '') | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are no longer required as they are handled by the new
plugin:clean-duplicate-gemstask.