Add prerelease profile and update release profile

[hesara]

This change is 

[elmot]

Review status: 0 of 1 files reviewed at latest revision, 2 unresolved discussions.

---

pom.xml, line 587 at r1 (raw file):

                <rules>
                  <requireMavenVersion>
                    <version>(,2.1.0),(2.1.0,2.2.0),(2.2.0,)</version>

Do we really support Maven 2? Isn't it better to support maven starting from from 3.3 or something?

---

pom.xml, line 667 at r1 (raw file):

                <rules>
                  <requireMavenVersion>
                    <version>(,2.1.0),(2.1.0,2.2.0),(2.2.0,)</version>

See above about mvn version

---

Comments from Reviewable

[hesara]

Review status: 0 of 1 files reviewed at latest revision, 2 unresolved discussions.

---

pom.xml, line 587 at r1 (raw file):

Previously, elmot (Ilia Motornyi) wrote…

Do we really support Maven 2? Isn't it better to support maven starting from from 3.3 or something?

This only excludes the buggy Maven versions, and is identical to how we do it in the parent POM. Until a few weeks ago, the plug-in was still compilable with Maven 2, but as that is no longer the case, I'll simplify the configuration in the Maven plug-in POM. The parent POM (not used by the plug-in) will still have this as it also applies to many other projects, some of which are Maven 2 compatible.

---

pom.xml, line 667 at r1 (raw file):

Previously, elmot (Ilia Motornyi) wrote…

See above about mvn version

see above

---

Comments from Reviewable

[elmot]

---

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

---

Comments from Reviewable