First idea of scim schema extension representation
Add release profile and move nexus-staging-plugin into it
Move maven-release-plugin into release profile. Point distribution repos to internal systm fow now to avoid clutter on sonatype
Add integration profile that uploads snapshots on maven-repo.evolvis.org
Remove duplicate definition of maven-deploy-plugin, mergin the dependency setting towagon
Add wagon extension
Set differing pathname for repo in fork as a marker to differentiate from integration profile
Cosmetics: make profiles better readable in editor
Add default setup for maven-release-plugin to override parent pom and not drop into sonatype-oss-release profile. Therefore no signing required without asking for it with the release profile. That's the idea, anyway...
We need to explicitly define arguments for the default plugin invocation lest we end up with the definition from pluginManagement in parent pom (which is merged into the invocation). Define empty property for release.arguments too
add override definition for maven-release-plugin, do not attempt to use releaseProfiles, fill release.arguments property with dummy value
Point fork's publishment to real directories on maven-repo.evolvis.org, needed for life jenkins build runs
have scm entry point to fork to make perform:release push into the fork and not the original git repo
Bump snapshot release to skip over possible clutter
[maven-release-plugin] prepare release scim-schema-0.23.3
[maven-release-plugin] rollback the release of scim-schema-0.23.3
[maven-release-plugin] prepare release scim-schema-0.23.3
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] rollback the release of scim-schema-0.23.3
[maven-release-plugin] prepare release scim-schema-0.23.3