This is an automated email from the ASF dual-hosted git repository.
elharo pushed a change to branch replace
in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git
discard 5d8b794e check for null
discard 9b5adffd Prefer JDK replace method over deprecated StringUtils method
omit 5e0f9a0d Remove commented code
new 2c18e899 Prefer JDK replace method over deprecated StringUtils method
new 43f607c6 check for null
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 (5d8b794e)
\
N -- N -- N refs/heads/replace (43f607c6)
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 2 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:
.../plugins/javadoc/stubs/CustomConfigurationMavenProjectStub.java | 2 ++
1 file changed, 2 insertions(+)
