Version 0.8.3

You can now use Lazybones with an authenticating proxy. Simply add the following properties to your Lazybones configuration:

systemProp.http.proxyUser = "<username>"
systemProp.http.proxyPassword = "<password>"

in addition to http.proxyHost and http.proxyPort.

Version 0.8.2

You can now set http.proxyPort to an integer value inside your Lazybones config.groovy file. Previously, it has to be a string.

Version 0.8.1

You can now configure system properties via your Lazybones configuration file by using the systemProp. prefix. This is particularly useful for configuring a proxy for HTTP access. For example:

systemProp {
    http {
        proxyHost = "localhost"
        proxyPort = "8181"
    }
}

This is the same approach as taken by Gradle.

Version 0.8

Version 0.8 of Lazybones brings you one major feature: config commands! As described in issue #118, these allow you to view and manipulate the current saved configuration using the command line. The available commands are:

config set <option> <value1> ...
config add <option> <value1> ...
config clear <option>
config show [--all] <option>
config list

• set updates the value of a single setting.
• add appends an extra value to an array/list setting
• clear removes a setting
• show displays the current value of a setting (--all displays the current values of all stored settings)
• list displays all available settings that you can change

You can still use the standard user-defined configuration file (~/.lazybones/config.groovy), it's just that there is an additional JSON config file that can be updated programmatically. Note that settings in the Groovy file override those in the JSON file. You can also manually edit the JSON file if you'd prefer to keep all your settings in that.

In addition to config commands, this release now handles null versions of a package in Bintray (issue #136). This shouldn't really happen, but at least when it does the Lazybones error output now hints that the latest version may be null.

Gradle Plugin Version 1.2.3

This is a small patch release that:

• fixes some issues with file paths in post-install scripts (issue #130)
• allows users to run the plugin on Java 6
• safely handles template directories that don't fit the plugin's naming convention (issue #138)

Gradle Plugin Version 1.2.2

Fixes sub-template packaging. In so doing, the plugin now supports a new configuration property for the build that allows users to specify the version for a template:

lazybones {
    template("simple-java") {
        version = "1.0.0"
    }
}

Note that this property is template-specific.

Version 0.7.1

This is a patch release to fix some critical file locking issues on Windows.

Gradle Plugin Version 1.2.1

This is an important patch release that fixes the publishTemplate* tasks.

Gradle Plugin Version 1.2

This version of the plugin introduces several new features and fixes. Most importantly, it is now qualified, so you will need to use:

apply plugin: "uk.co.cacoethes.lazybones-templates"

Features and fixes:

• You can specify files and directories that should be excluded when packaging templates
• You can specify file permissions for the files and directories in the template packages
• Template directories are no longer validated during configuration, but rather at execution time
• You can use numbers in template names, e.g. 'standard-neo4j'

There are two forms for the exclusions and file permissions (global and per template):

lazybones {
    // Global
    packageExclude "**/*.swp", "**/*.swo"
    fileMode "755", "gradlew", "gradlew.bat"

    // Per template
    template("ratpack") {
        packageExclude ".gradle", ".settings" 
        fileMode "755", "gradlew"
    }
}

As for templates with numbers in them, consider a template directory with the name "standard-neo4j". The corresponding tasks would be named:

packageTemplateStandardNeo4j
installTemplateStandardNeo4j
publishTemplateStandardNeo4j

If you instead what numbers separated by hyphens, e.g. "javaee-7", then you need to use the hyphenated form in the task names:

packageTemplate-javaee-7

The installTemplate* and publishTemplate* tasks may not work in this case, but it's easy enough to generate them in your build file.

Version 0.7

Version 0.7 is a significant release that introduces sub-template support via a new generate command. It's geared towards allowing users to generate extra files in their project after the initial project creation. Project templates can use it to generate entity or controller classes for example.

In addition:

• Added template name qualifiers, e.g. lazybones generate artifact::controller (with 'controller' being the qualifier)
• Added a --cached option to the list command that displays the cached templates
• Improved behaviour of create, list and info when a user is offline.
• targetDir in scripts is deprecated and replaced by projectDir (of type File rather than String)
• Added templateDir for scripts, which points to the location of the unpacked sub-template (has the same value as projectDir for project templates)
• Added tmplQualifiers for scripts that contains template name qualifiers

Please review the project README, the template developers guide and the Gradle plugin's README to find out more about the new features.