Sync template version with latest Spring Boot.
Merge branch 'master' of https://github.com/tbarker9/lazybones
Remove out of date publishing info from README

The template developers guide on the wiki has all the important information on
creating and publishing templates, so there is no need to have it in the README.
And the README info was way out of date too.
Correct the build instructions for the templates.

The build information for packaging and publishing the included templates was out
of date, so I've updated it for latest Gradle tasks and rules.
Fix how numbers are handled in text transformations.

Conversions between hyphenated and camel-case forms didn't seem to handle
numbers correctly. I've now clarified the expected behaviour in both javadoc
and the class specification. I have also updated the specification to verify
the handling of numbers.
Bump Gradle plugin version to 1.0.4.
Add support for sub-templates.

Implementation of issue #86. Sub-templates are just like normal project
templates, except they are not published separately. Instead, they are included
directly in a project template package.

The user can run the new `generate` command to activate a sub-template whose
job it is to actually do something, such as create new files in the project.
The user can also pass in parameters if the sub-template uses the `ask()`
method.

The Gradle plugin for managing Lazybones templates now allows you to define
relationships between main templates and sub-templates. The sub-templates are
packaged separately and then included into the main template package zip.

You create sub-templates as normal templates except that the directory name
must begin with 'subtmpl-'. This ensures that they aren't included in the
`packageAllTemplates`, `installAllTemplates` and `publishAllTemplates` as they
shouldn't be published independently. You then use the Lazybones extension to
declare that a template includes some set of sub-templates. The plugin does
the rest.
Remove '-template' from package name only if suffix.

The rule/task for installing templates was removing the string '-template'
from any part of the template name, not just if it was a suffix.
Use appropriate capitalisation for rule descriptions.

The descriptions for the Gradle plugin's rules used camel case with an initial
lowercase letter, e.g. installTemplate<tmplName>. But the user has to specify
the template name with an initial capital letter, such as installTemplateDummy.
So now the rules are like installTemplate<TmplName> to avoid confusion.
Rename integTests task to integTest for consistency.
Add support for template name qualifiers

When using the `create` or `generate` command, users can include extra info
with the template name, e.g. generate artifact::controller. In this example,
the template name is 'artifact' and there is one qualifier, 'controller'.

The qualifiers are available to templates via the new `tmplQualifiers` property
on `LazybonesScript`.
Use Gradle distribution with docs included.
Sort templates alphabetically in `list` output.

The `list` command was just displaying templates in the order that Bintray
returned them. Bintray may have returned them in alphabetical order, but it's
definitely not doing that at the moment. So `ListCommand` now sorts the
template names itself.
Merge stdout and stderr for functional tests.

It was difficult to verify the order in which Lazybones printed stuff to the
console, particularly with stacktraces, because two separate threads were
consuming the output from stderr and stdout. This often left stacktraces and
normal output interleaved.

I now use `ProcessBuilder` explicitly and configure it to merge stdout and
stderr, which eliminates the interleaving problem.
Handle case when `generate` called in wrong directory.

The `generate` command has to be invoked within a directory that has a
.lazybones sub-directory. Although no exception was thrown in this case, the
error was hardly informative. This case is now explicitly handled with an
appropriate message that tells the user that they are not running the command
in a Lazybones-created project directory.
Support offline usage properly.

Implements issue #67. The `create`, `list` and `info` commands now gracefully
fail with suitable error messages if Lazybones is running offline. In fact, the
`list` command will still work, it just won't display remote templates.
Support creating packages in Bintray.

Implements issue #112 and I think it fixes issue #111 as well.

The Gradle plugin now automatically creates a package in Bintray if it doesn't
already exist. For this to work, you have to specify a `licenses` property in
the `lazybones` block.

You can also now specify just a Bintray repository name rather than a complete
repository URL. This takes the form "<user>/<repo>".
Bump Gradle plugin version to 1.1.
Update projects to use Gradle plugin 1.1.
Fix README since repo.url no longer required.

When publishing the templates in the lazybones-templates subproject, you no
longer need to specify a repository URL. So this requirement has been removed
from the README.