This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/commons-io-commons-io-2.7
in repository https://gitbox.apache.org/repos/asf/maven-ejb-plugin.git
omit e516e7c Bump commons-io from 2.6 to 2.7
add fdb287f [MEJB-133] Upgrade to Java 8
add cd809c9 [maven-release-plugin] prepare release maven-ejb-plugin-3.2.0
add 9b5ddd5 [maven-release-plugin] prepare for next development iteration
add 44d4bc2 Upgrade Parent to 35
add a55e15f [maven-release-plugin] prepare release maven-ejb-plugin-3.2.1
add 4b2ad1b [maven-release-plugin] prepare for next development iteration
add fe7c7ba Fix site "usage" page
add 20a4cbf (doc) fix ci
add fbcc5b6 update Reproducible Builds badge link
add 24624b2 Bump commons-io from 2.6 to 2.7
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 (e516e7c)
\
N -- N -- N
refs/heads/dependabot/maven/commons-io-commons-io-2.7 (24624b2)
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:
README.md | 2 +-
pom.xml | 16 +++++++++-------
src/it/mejb-34-filtered/{verify.bsh => verify.groovy} | 0
.../mejb-34-not-filtered/{verify.bsh => verify.groovy} | 0
4 files changed, 10 insertions(+), 8 deletions(-)
rename src/it/mejb-34-filtered/{verify.bsh => verify.groovy} (100%)
rename src/it/mejb-34-not-filtered/{verify.bsh => verify.groovy} (100%)
