Here is the 1.8.0 release log...all glorious 81 steps of it:
https://docs.google.com/document/d/10LkAD8Wk5Kcj38nQghTW-bQdCOXaxZad5W5Chu6HUCA/edit?usp=sharing
Looking through it, the immediate things we need to address to make
this easier, as far as I can see, are:
1. Ensure the Maven release plugin stops prompting. This basically
means getting rid of ${project.parent.version}-type versions in POMs
2. Use a consistent structure to allow for uniform bumping of core
versions in downstream repos. E.g. at present, jclouds.version needs
to be updated for some repos (and then in different places! Sometimes
in pom.xml, other times in project/pom.xml etc.), mvn
version:update-parent run for others etc.
3. Remove any self-dependencies caused by javadoc:aggregate in the
aggregator POM. This means either going (back) to a project POM per
repo, or to inheriting from jclouds-project as labs-openstack does.
If we can get this done, we should at least be able to run pretty much
the same set of commands for each repo, with only a couple of
exceptions (e.g. no bumping of dependency versions for core).
Regards
ap
