Skip to content

Commit 48b0be8

Browse files
committed
[build] Prefer compile against jruby-complete due to bundler-maven-plugin quirks
We only need the deconstructed variant, but bundler-maven-plugin has a quirk where it only filters jruby-complete from forked process which we need to compile targetting one JRuby version, but run tests on another.
1 parent df94627 commit 48b0be8

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

pom.xml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,9 @@
7676
<dependencies>
7777
<dependency>
7878
<groupId>org.jruby</groupId>
79-
<artifactId>jruby</artifactId>
79+
<!-- This has to be jruby-complete, as bundler-maven-plugin has special logic to exclude jruby-complete - otherwise
80+
it conflicts with the bootclasspath if using different "target compile version" to "runtime version" -->
81+
<artifactId>jruby-complete</artifactId>
8082
<version>${jruby.version}</version>
8183
<scope>provided</scope>
8284
</dependency>

0 commit comments

Comments
 (0)