This is an automated email from the ASF dual-hosted git repository. slachiewicz pushed a change to branch MANTRUN-225 in repository https://gitbox.apache.org/repos/asf/maven-antrun-plugin.git.
omit 0c37be3 [MANTRUN-225] Upgrade Apache Ant to 1.10.7 omit 8fc2aee [MANTRUN-224] Upgrade tests to JUnit5 omit e9ea05a [MANTRUN-224] Require Java 8 omit f2b3605 Prepare for 3.1.0 add 47c4610 set Maven 3.1.1 as minimum version add 1e63614 Merge pull request #6 from apache/v add 7d195b0 deps: update hamcrest add b3582e8 Merge pull request #7 from apache/elharo-patch-1 add d0dfc73 Prepare for 3.1.0 add c6e5f34 [MANTRUN-224] Require Java 8 add 171bb21 [MANTRUN-224] Upgrade tests to JUnit5 new 7d24b49 [MANTRUN-225] Upgrade Apache Ant to 1.10.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 (0c37be3) \ N -- N -- N refs/heads/MANTRUN-225 (7d24b49) 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: pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)