Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4233
`mvn verify` _should_ run all tests since the default for all added
properties is true. But yes, it currently doesn't. I don't quite understand
this as the default for all groups is true (i.e. all test profiles should
activate) and I'm not modifying the phases of these profiles.
Maven's `-am` and `-amd` options don't work for us since these don't build
dependencies marked as provided, i.e. most core flink dependencies. You can
easily verify this yourself.
Maven's `-pl` command is a bit brittle in general as we have to include
every single module; we can't just point to flink-libraries and call it a day.
This adds a maintainability problem; a new module will not be tested on travis
if the contributor/reviewer isn't aware of the magic in the travis scripts.
This is less likely with the approach in this PR as part of the magic is in the
poms which are more likely to be seen by a developer.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
