1.2.4 (Jun 22, 2015)
No release notes available for this version yet.
1.2.3 (Dec 17, 2014)

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)

1.2.2 (Aug 25, 2014)

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.

1.2.1 (Aug 24, 2014)

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

1.2 (Aug 23, 2014)

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:


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

1.1 (Jun 18, 2014)

The biggest changes for this release is the new support for packaging
sub-templates to coincide with the 0.7 release of Lazybones.

In addition:

  • When publishing, the plugin will now attempt to create the package in Bintray if it doesn't already exist.
  • Fixed a bug where a project template with '-template' in its name couldn't be used because the '-template' was removed on installation.
1.0.4 (Jun 04, 2014)

Simply defaults to a value of false for the new publish property, which means that templates are not automatically published on Bintray once they have been uploaded. With this setting you need to manually publish the templates from the Bintray UI.

1.0.3 (Jan 06, 2014)

This release just adds a publish property to the BintrayUpload task that determines whether an artifact should be published automatically once uploaded.

1.0.2 (Aug 02, 2013)
No release notes available for this version yet.
1.0.1 (Jul 02, 2013)
No release notes available for this version yet.
1.0 (Jun 21, 2013)
No release notes available for this version yet.
0.1 (Jun 21, 2013)
No release notes available for this version yet.