- Use the new 1.0.0-alpha.1 Grolifant release that has configuration-cache
safety built-in.
- Check that no usage of `Project` object will be done after configuration
phase has ended.
- Maintain compatibility down to Gradle 4.3.
- `JRubyPluginExtension`
- `JRubyExec`
- Split out `GemUtils.OverwriteAction` into its own class `GemOverwriteAction`.
- Moved `GemUtils` to `core-plugin`.
- Removed `RubygemsServlet`.
- Reworked `GemVersion` to be more Ivy-like rather than Maven-like.
- Reworked `JRubyPrepare` & `JRubyExec`.
- Extract common `JRubyPrepare` code to `AbstractJRubyPrepare`.
- Cleaned up `JRubyExec` to no longer depend on `JRubyExecTraits`.
- Cleaned up `JRubyExecDelegate` to no longer depend on `JRubyExecTraits`.
- In `JRubyPlugin`, register tasks instead of creating them if Gradle supports lazy-creation.
- Removed last usages of `jar-dependencies`.
- Cleaned up integration tests and unit tests
- Resolve dependencies with transitive dependencies.
- Added a repository handler extension for defining rubygems.
- Protect ivy.xml file creation against concurrent access from threads of multiple processes.
- Support all known GEM version requirement formats
- 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.
Uwe Kubosch
Uwe Kubosch
Schalk W. Cronjé
R Tyler Croy
aalmiray
Christian Meier