GitHub user kennknowles opened a pull request:

    https://github.com/apache/incubator-beam/pull/572

    Update surefire plugin to 2.19.1

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    I noticed that we were using a very old version of surefire. The latest 
version is still 6 months old, so nothing like bleeding edge. It adds simple 
things like excluding tests by fully qualified class name, which is nicer than 
file path patterns.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kennknowles/incubator-beam surefire

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-beam/pull/572.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #572
    
----
commit 37e266e58a6d3da4e0bcf5426983dc130befd387
Author: Kenneth Knowles <[email protected]>
Date:   2016-07-01T03:58:09Z

    Update surefire plugin to 2.19.1
    
    This version is the most recent, still very old (6 mo), and
    is the first version that allows test exclusion by fully
    qualified class name.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to