Releases: rholder/gradle-view
Releases · rholder/gradle-view
Release 4.0.0
Notes
- Upgrade internal tooling API to use Gradle 5.6.2 which adds Java 11 support
- Gradle wrapper is now at Gradle 5.6.2
- Java bytecode compatibility bumped up to 1.8 to support later versions of Gradle Tooling API
- Switch to using the org.jetbrains.intellij plugin for more modern plugin development
- Removed old gradle-one-jar plugin in favor of shadow
Known Issues
- Gradle 4.x and below don't support Java 11 and recent versions of the IntelliJ Platform now ship with the Jetbrains Runtime (JBR) which is based on Java 11. Using Java 8 and an IntelliJ Platform that does NOT include the bundled JBR may provide a workaround for some issues with older JDKs.
SHA256
498ce616cf9033fdc96a0fb58c1a3742975fa731c8707a8546c7231ca649ea61 gradle-view-4.0.0-standalone.jar
93cffad357c3bd1591ef23fd7a6be6883a838b585425b1c2e40105dc1279992e gradle-view-4.0.0.zip
Release 3.0.0
Notes
- Upgrade internal tooling API to use Gradle 3.5.1
- Add dependency resolution compatibility fixes to support Gradle 2.x, 3.x, and 4.x
- Java bytecode compatibility bumped up to 1.7 to support later versions of Gradle Tooling API
Known Issues
- Lightly tested on a few Gradle 1.x, 2.x, 3.x, and 4.x projects, the same bugs for previous releases probably still apply
Release 2.1.0
Notes
- Upgrade internal tooling API to use Gradle 2.3 #11
- Backward compatibility with Gradle 1.x projects
- Remove painful light red on blue background selection color #6
Known Issues
- Gradle plugins in your build compiled with Java 1.7+ source compatibility don't work under IntelliJ for Mac since it still runs the Gradle Tooling API with the Java 1.6 runtime
Release 2.0.2
Notes
- Bug fix release, no new features added since 2.0.0
- Fixed some wonky Windows JAVA_HOME path behavior #5
Known Issues
- Gradle plugins in your build compiled with Java 1.7+ source compatibility don't work under IntelliJ for Mac since it still runs the Gradle Tooling API with the Java 1.6 runtime
Release 2.0.1
Notes
- Bug fix release, no new features added since 2.0.0
- Fixed a Windows path bug with absolute file names #5
Known Issues
- Gradle plugins in your build compiled with Java 1.7+ source compatibility don't work under IntelliJ for Mac since it still runs the Gradle Tooling API with the Java 1.6 runtime
Release 2.0.0
Notes
- Completely rewritten Gradle Tooling API integration
- Seamless custom Gradle Tooling API model that injects itself into a project without modification
- Better UI arrangement by combining trees in the left pane with more intuitive naming
- Added a scrolling log window
- Fixed bug where rendered tree nodes are truncated when toggling replacement view
- Feature parity with old
1.0.x
Known Issues
- Gradle plugins in your build compiled with Java 1.7+ source compatibility don't work under IntelliJ for Mac since it still runs the Gradle Tooling API with the Java 1.6 runtime
Release 2.0.0-beta3
Notes
- Feature parity with old
1.0.x
- Better tree UI arrangement
- Fixed bug where rendered tree nodes are truncated when toggling replacement view
Release 2.0.0-beta2
Notes
- Completely rewritten Gradle Tooling API integration
- Seamless custom Gradle Tooling API model that injects itself into a project without modification
- UI improvements: more intuitive nameing, combined trees in the left pane, addition of a scrolling log
Known Issues
- Sorting for the
Dependency Hierarchy
tree seems a bit off