for lazy people, I took time to create the 4 repo on personal GitHub space:
https://github.com/hboutemy/maven-apache-parent
https://github.com/hboutemy/maven-parent
https://github.com/hboutemy/maven-default-skin
https://github.com/hboutemy/maven-fluido-skin
I won't do the same in the future for th
hboutemy closed pull request #4: [MRELEASE-798] Commit additional files with
release plugin
URL: https://github.com/apache/maven-release/pull/4
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As t
hboutemy closed pull request #13: MRELEASE-980 Allow commit comments to be
controlled
URL: https://github.com/apache/maven-release/pull/13
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this i
As you probably noticed, I migrated maven-dist-tool [1] to git, using self-
service Gitbox for the empty repo creation and a migrate-sandbox.sh shell
script [2] to populate them (after Sling example)
It worked like a charm!
If nobody objects, in 72h, I'll use migrate-pom.sh and migrate-skins.sh
