## How it works?
- Uses the fixed versions to clone and check out each project (e.g. `spring-cloud-sleuth: 2.1.0.RELEASE`)
- From the version analyzes the branch and checks it out. E.g.
- for `spring-cloud-release`'s `Finchley.RELEASE` version will resolve either `Finchley.x` branch or will fallback to `master` if there's no `Finchley.x` branch.
- for `spring-cloud-sleuth`'s `2.1.0.RELEASE` version will resolve `2.1.x` branch
- Performs the release tasks per each project
- Performs the post release tasks at the end of the release
## Required options
- `releaser.fixed-versions` - A String to String mapping of manually set versions. E.g. `"spring-cloud-cli" -> "1.0.0.RELEASE"` will set
the `spring-cloud-cli.version` to `1.0.0.RELEASE` regardless of what was set in `spring-cloud-release` project. Example `--releaser.fixed-versions[spring-cloud-cli]=1.0.0.RELEASE`.
Use these properties to provide versions for the meta release.
- `releaser.meta-release.enabled` - You have to turn it on to enable a meta release. Defaults to `false`
- `releaser.meta-release.git-org-url` - The URL of the Git organization. We'll append each project's name to it.
Defaults to `https://github.com/spring-cloud`
run the task via `-x=true`
without this change the only way to execute tasks is to provide their number from the console
with this change we can provide execution options from the command line, we can execute full releases, single steps, multiple steps, bounded and unbounded ranges
fixes#37fixes#44
prerequisite for #30
with this change it's enough to pass `releaser.fixed-versions` with a projectName->version mapping. This will override anything that came from spring cloud release
fixes#16
without this change we could commit a release version that references a dependency in a snapshot version
with this change an exception will be throw in such a case. Exception will contain a file name together with the line in which a snapshot version was found
fixes#7
