- Upgradle to 4.8.1.
- Remove lasagne GEMS proxy.
- Remove `buildscript`, replace with `plugins`.
- Source/target compatibility set to JDK8.
- Upgradle to Grolifant 0.8.
- Upgradle to Spock 1.1.
- Added Gradle 4.9 to compatibility test set.
- Remove deprecated CodeNarc rules.
i
- Use Torquebox in addition to lasagne,io when building and to work around
flasky tests.
- Use Grolifant library to deal with Gradle compatibility issues.
- Remove Gradle 5.0 deprecation warning.
- Do not set logging level within tests.
- Ignore IntelliJ "out" directories.
- Update GradleTest fixtures for 1.0-betaX improvements.
- Split out JRubyPluginInstanceSpec to its own file.
- Extract JRubyJarTestKitSpec into its own test file.
- Make test repository preparation a separate task.
- Update TestKit syntax to deal with Gradle 4.2.
- State that Gradle 2.8 is a minimum version.
Also marked custom repository test as `PendingFeature` to be investigated
later as doe a possible rewrite.
The maven plugin doesn't give us (AFAICT) the necessary pom manipulation
capabilities to change the artifactId to 'jruby-gradle-plugin' instead of
project.name
Fixes#195
basically it sets up the jars in the same manner as it would pack it inside a jar
and uses the usual loading semantic for loading jars with jruby. and with this
the jrubyExec task does not need interfer with those embedded jars coming with
jruby itself like bouncycastle jars, jline jar or snakeyaml jar.
fixes#123 and #113