build(maven): configure maven release plugin commit prefix

[ChristianMurphy]

this avoids a conflict between the conventional commit message linter and the maven release plugin.

resolves #682

---

Contributor License Agreement adherence:

• This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

[davidmsibley]

can we have it as chore(release): [maven-release-plugin] or will that still break the commit hook?

[ChristianMurphy]

It would still break, this time with the title length.

chore(release): [maven-release-plugin] prepare release angularjs-portal-parent-6.6.0

is 84 characters log, header max length is expected to be <72 characters.
ref: https://github.com/marionebl/commitlint/blob/e6ef0721a230b90fc17955b33983c8bea2767d7f/%40commitlint/config-angular/index.js#L7

[ChristianMurphy]

@davidmsibley
I'm taking an educated guess that you want to preserve information that release commits were autogenerated.
Would setting scm username for the release commits to Maven Release Plugin communicate that effectively?

📓 That would remove the record of who cut the release.

[davidmsibley]

I'm trying to figure out if my hesitation here is rational. I know that we do have more than a couple of internal Jenkins jobs that parse commit messages and look for that standard maven release formatted commit message. But those jobs don't run on these repos, so I kind of think it'll be fine. Anytime you're changing from a standard format to custom, it warrants a little thought because it could hurt you down the line. I'm reminded of a recent discovery by a coworker that he couldn't easily import years of server logs into a log summarizer/visualizer because on day one they'd decided to tweak the apache log format a bit to add more information (thus breaking the OOTB log parser).

There may be some irrational fear here as well. At the moment I place little to no value in commit message linting, and I despise commit hooks. So the idea that we change our build system to accommodate them is unpleasant. Maybe someday in the near future the value of commit message linting will become clear and I'll love it the same way I changed my opinion on Greenhopper the moment it started opening pull requests.

tl;dr: I've become a curmudgeon, and maybe when @vertein and @apetro get back in to the office tomorrow you'll get a better review 😄

[apetro]

How much longer are we going to keep using Maven to release a product that's got nothing to do with Java? The sooner we turn the corner, the sooner this is moot and we get to re-solve these problems with other releasing tools. 😄

[vertein]

Let's do it. I understand some reservation. I think we do this until we stop using the maven plugin anyways.