o flipping groupId to io.tesla.maven, adjusting distribution management and scm
o correct scm element
[maven-release-plugin] prepare release maven-3.1.0
[maven-release-plugin] prepare for next development iteration
added a notice for the MSITE-687 workaround
o correct scm element. we will build the tesla distribution as close to a stock maven build as we can but we can't rely on the release cycles at apache and we want to able to turn around builds and fixes as fast as possible.
o look for the properites in maven-artifact and not in maven-core. during testing the pom.properties is not present because it's created by the JAR plugin.
o look for the io.tesla.maven groupId
o correct scm element
[maven-release-plugin] prepare release maven-3.1.1
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-3.1.2
[maven-release-plugin] prepare for next development iteration
maven-site-plugin 3.3 released
use maven-project-info-reports-plugin 2.7, which has better git support
maven-dependency-plugin 2.8 released, now compatible with Eclipse Aether
[MSITE-484] reporting section cannot be deprecated in Maven core for the
moment
[MNG-5480] added documentation about default url values calculated
from parent pom
more sensible value for version: 4.0.0+ instead of 4.0.0, since
the vast majority from actual pom version will remain in future versions
added a note about module=artifactId recommendation