This is an automated email from the ASF dual-hosted git repository. slachiewicz pushed a change to branch MJDEPRSCAN-7 in repository https://gitbox.apache.org/repos/asf/maven-jdeprscan-plugin.git
discard f63619e [MJDEPRSCAN-7] Bump plexus-utils, commons-lang3 and junit to latest versions discard 062aec6 [MJDEPRSCAN-6] Require Maven 3.2.5+ omit be23b29 [MJDEPRSCAN-5] Require Java 8 add e61b608 [MJDEPRSCAN-5] Require Java 8 add 94f5e81 (doc) cleanup toolchain setup add fde8992 [MJDEPRSCAN-6] Require Maven 3.2.5+ new e8fd00d [MJDEPRSCAN-7] Bump plexus-utils, commons-lang3 and junit to latest versions 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 (f63619e) \ N -- N -- N refs/heads/MJDEPRSCAN-7 (e8fd00d) 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 1 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: .github/workflows/maven.yaml | 50 +++++----------------- .../plugins/jdeprscan/AbstractJDeprScanMojo.java | 2 +- 2 files changed, 12 insertions(+), 40 deletions(-)