This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a change to branch DOXIA-602
in repository https://gitbox.apache.org/repos/asf/maven-doxia.git.


 discard a49fb7b  [DOXIA-602] Missing test
 discard 03a201f  [DOXIA-602] More improvements to tests
 discard 855e044  [DOXIA-602] Code improvements for Junit
 discard e823450  [DOXIA-602] Upgrade to XMLUnit 2.6.3
 discard 77cec36  [DOXIA-602] Upgrade to JUnit 4.13
     add b73bacb  [DOXIA-595]  fixed site build on Windows  - xdoc
     add fdbe5d4  [DOXIA-601] Use parent-pom version for changes-plugin 2.12.1
     new 40f42bf  [DOXIA-602] Upgrade to JUnit 4.13
     new 99043de  [DOXIA-602] Upgrade to XMLUnit 2.6.3
     new 31beadf  [DOXIA-602] Code improvements for Junit
     new 751e544  [DOXIA-602] More improvements to tests

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   (a49fb7b)
            \
             N -- N -- N   refs/heads/DOXIA-602 (751e544)

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 4 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:
 doxia-modules/doxia-module-fml/pom.xml  |  4 ++--
 doxia-modules/doxia-module-xdoc/pom.xml | 17 ++++-------------
 pom.xml                                 |  3 +--
 3 files changed, 7 insertions(+), 17 deletions(-)

Reply via email to