0.0.7 - Regression when evaluating .groovy files outside gradle projects

Bugfixes

Fixed a regression that caused evaluation of .groovy files residing outside a connected gradle project to fail spectacularly. It tried to connect to the .groovy file as a gradle project and that obviously would never work.

Switching evaluation between different .groovy files outside a gradle project will not be as fast as it should though. Because it closes connection and makes a new connection when changing .groovy file. Need to look into the LightTable client/connection handling stuff to be able to provide a decent fix for that.

0.0.6 - Gradle dependency graph and multiproject task execution

Changes

Gradle dependency graph

View your gradle project dependencies in a Dot graph. You can view dependencies for each configuration and for multiprojects you can get an overview and a simple drilldown feature.

Execute tasts / task selectors in Gradle multiprojects

During Hackergarten at gr8conf a couple of cool contributions were made. One of which was listing tasks for multiprojects. This has been extended to also display task selectors (to make it as easy as on the command line to execute say the "build" task for all your projects in one go.

Minor changes

• Use file.encoding=UTF-8 when running the groovy client
• Use runtme classpath from gradle model sourceSet. Any customizations in build scripts should now be safely handled !

Technical notes

• For graphing d3 and more specifically dagre-d3 has been used.
• A custom gradle model plugin has been build to provide richer model information than you default get through the gradle tooling api. Feel free to check out : generic-gradle-model

0.0.5 - Gradle task execution

Changes

• You can view a list of available tasks with descriptions for a connected gradle project
• Its now possible to execute gradle tasks for a Gradle project you have connected to. See the gradle chapter in the readme for more details. The gradle task integration works for any gradle project btw (java, scala, groovy whatever) !
• When loading classpath progress is also reported. This is an improvement over 0.0.4

Fixes

• Fixed run-server script for certain setups through pull request from @gregopet

Behind the scenes

• Custom logging replaced with logback
• Refactored task invocation to a command-like pattern
• Embracing asynch features of gradle

0.0.4 - Gradle classpath integration

Changes

• You can now connect to gradle projects. This gives you access to calling classes in the classpath of your gradle project
• Methods are stored as closures in the bindings for each evaluation

Fixes

• Display of more that 10 values for iteration evaluations was mangled

0.0.3 - A hint of REPL

Changes

• Binding variables are stored between evals. This allows for a certain degree of a REPL like experience. It's still always compiles to groovy scripts so the same limitations as groovy scripts apply
• You may clear binding variables for an editor

Fixes

• Some tests failed intermittently due to assertions on hashmaps

v0.0.2 - Vastly improved display of inline results

Change log

• We show inline results for a range of statement types. Ast transformation of script used for collecting values for statements. Big thx to (Jim White) [https://github.com/jimwhite] for his contributions.
• If your script triggers an exception, inline results up until the exception are shown
• Groovy(/Java) code now has some automated tests using Spock
• Display of binding variables have been removed. Can't see that we need them (for now at least)
• The groovy client is now implemented as a jar started via Java rather than being just a groovy script.

v0.0.1 - Initial release with simple inline evaluation

Features

• Early alpha release with simplistic inline evalution of selected lines or whole editor
• Provides basic syntax highlighting

Disclaimers

Only tested on mac os x