[BEAM-806] update archetype poms in master

[dhalperi]

Per the linked JIRA, maven release:branch did not do the right thing.

R: @aljoscha
CC: @davorbonaci

[davorbonaci]

LGTM.

Do we know why? I don't remember doing this myself.

[dhalperi]

CC: @lukecwik @peihe

From Luke:

The problem with the previous version was that our archetypes were not being maintained, and it was incorrect to say that they were compatible across those ranges because of all the backwards incompatible changes

This is completely true, and the process of fixing it manually in master works. But this does not help the release process, which is specifically designed to use mvn release to do all updating of versions repository-wide.

[aljoscha]

LGTM for master but it doesn't solve my problem with the 0.3.0-incubating release because the plugin does all the version juggling between 0.3.0-incubating-SNAPSHOT and 0.3.0-incubating. I could try working around that manually but I feel that a proper fix would be good there.

On a side note, it's somewhat strange that the release plugin pushes everything to git right-away without giving me a chance to correct things. (I know that this is documented in the release guide and I knew it when executing the command, but still...)

[davorbonaci]

Totally agree that automatic pushes are not a great idea. There's a manual flag to disable them. It would be great if all this went through pull requests, but that appears to be non-standard. I'm hopeful we can improve this in the near future.

[dhalperi]

At the same time, manual fixup of PRs is not reproducible across different committers or releases... a platonic release process would be fully automated. We ought to fix the process such that even if done in PRs we are not needing to do anything but rubber stamp; and we would catch breakages to the release process earlier. Maybe we can do some of this with the nightlies, like testing that we can run mvn release:prepare and that it compiles?