This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch remove-default-skin
in repository https://gitbox.apache.org/repos/asf/maven-site-plugin.git
discard edeaf211 Last fix
discard 8b1ff122 ss
discard f2072278 First shot
add fb180da9 update history+migrate for m-site-p 4.0.0-M1
add 65a80522 [MSITE-902] Upgrade Plexus Utils to 3.4.2
add 4a38a81f [MSITE-901] If preceding standalone report has been run,
site:jar does not reinvoke site:site
new c6956307 First shot
new 0c4ce46a ss
new 86952e41 Last fix
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (edeaf211)
\
N -- N -- N refs/heads/remove-default-skin (86952e41)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 2 +-
.../{MSITE-354 => MSITE-901}/invoker.properties | 2 +-
src/it/projects/{MSITE-723 => MSITE-901}/pom.xml | 43 +++++++++-------------
.../{MSITE-723 => MSITE-901}/verify.groovy | 10 +++--
.../maven/plugins/site/render/SiteJarMojo.java | 7 +---
src/site/apt/history.apt | 6 ++-
src/site/apt/migrate.apt | 3 +-
7 files changed, 33 insertions(+), 40 deletions(-)
copy src/it/projects/{MSITE-354 => MSITE-901}/invoker.properties (96%)
copy src/it/projects/{MSITE-723 => MSITE-901}/pom.xml (62%)
copy src/it/projects/{MSITE-723 => MSITE-901}/verify.groovy (76%)
