This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a change to branch MCHANGES-453
in repository https://gitbox.apache.org/repos/asf/maven-changes-plugin.git
discard 0e74157 [MCHANGES-453] Align report output and goals names
add a7ca3ab [MCHANGES-453] Align report output and goals names
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 (0e74157)
\
N -- N -- N refs/heads/MCHANGES-453 (a7ca3ab)
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.
No new revisions were added by this update.
Summary of changes:
...Deprecated.java => ChangesDeprecatedReport.java} | 4 ++--
.../GitHubDeprecatedReport.java} | 19 ++++++++++---------
.../JiraDeprecatedReport.java} | 17 +++++++++--------
.../plugins/changes/trac/TracDeprecatedReport.java} | 21 +++++++++++++--------
4 files changed, 34 insertions(+), 27 deletions(-)
copy
src/main/java/org/apache/maven/plugins/changes/{ChangesReportDeprecated.java =>
ChangesDeprecatedReport.java} (91%)
copy
src/main/java/org/apache/maven/plugins/changes/{ChangesReportDeprecated.java =>
github/GitHubDeprecatedReport.java} (64%)
rename
src/main/java/org/apache/maven/plugins/changes/{ChangesReportDeprecated.java =>
jira/JiraDeprecatedReport.java} (68%)
copy src/{it/report-jira-invalid-issuemanagement/verify.groovy =>
main/java/org/apache/maven/plugins/changes/trac/TracDeprecatedReport.java} (65%)
