This is an automated email from the ASF dual-hosted git repository. slachiewicz pushed a change to branch min in repository https://gitbox.apache.org/repos/asf/maven-enforcer.git.
omit 3e94e4e Merge branch 'master' into min omit 157e3d6 update maven dependency tree add a3d57a4 Remove Travis config add 2742cb4 [MENFORCER-371] Require Maven 3.1.1 add d0349eb [MENFORCER-371] Update dependency to maven-compat add b49bd3b [MENFORCER-371] Drop dep to old plexus-container-default - use default new org.eclipse.sisu.inject one new 6c7b322 update maven dependency tree 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 (3e94e4e) \ N -- N -- N refs/heads/min (6c7b322) 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: .travis.yml | 33 ---------------------- enforcer-api/pom.xml | 5 ---- enforcer-rules/pom.xml | 2 ++ .../maven/plugins/enforcer/EnforcerTestUtils.java | 3 +- pom.xml | 7 +++-- 5 files changed, 7 insertions(+), 43 deletions(-) delete mode 100644 .travis.yml