beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-471) RAT misconfigured except in release profile
Date Tue, 19 Jul 2016 17:29:20 GMT


ASF GitHub Bot commented on BEAM-471:

GitHub user kennknowles opened a pull request:

    [BEAM-471][BEAM-472] Fixes to RAT configuration

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

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

    $ git pull RAT

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

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

    This closes #688
commit fffa7996318c4fc3a56b092b020c9270c15658c9
Author: Kenneth Knowles <>
Date:   2016-07-19T17:16:06Z

    Add fixed Eclipse RAT excludes

commit 1e162128a59dc3d01c772269ff4cdd6bb3e4b377
Author: Kenneth Knowles <>
Date:   2016-07-19T17:25:06Z

    Correctly configure RAT in all profiles


> RAT misconfigured except in release profile
> -------------------------------------------
>                 Key: BEAM-471
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Minor
> The configuration for RAT is isolated to the release profile. So, for example, the usual
invocation on the command line for interactive use will fail with confusing and erroneous

This message was sent by Atlassian JIRA

View raw message