nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-1511) Incorporate Groovy unit tests as part of the build instead of via profile
Date Fri, 26 Feb 2016 15:27:18 GMT

    [ https://issues.apache.org/jira/browse/NIFI-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169184#comment-15169184
] 

ASF subversion and git services commented on NIFI-1511:
-------------------------------------------------------

Commit 58e50ae39d5565592ae7b8368889209afab86e7c in nifi's branch refs/heads/master from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=58e50ae ]

NIFI-1511 Incorporating Groovy unit tests as part of the main build and providing explicit
compile scope on the Groovy dependency for the scripting bundle. This closes #220

Signed-off-by: Matt Gilman <matt.c.gilman@gmail.com>


> Incorporate Groovy unit tests as part of the build instead of via profile
> -------------------------------------------------------------------------
>
>                 Key: NIFI-1511
>                 URL: https://issues.apache.org/jira/browse/NIFI-1511
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Tools and Build
>    Affects Versions: 0.5.0
>            Reporter: Aldrin Piri
>            Assignee: Aldrin Piri
>             Fix For: 0.6.0
>
>
> From the mailing list:
> {quote}
> Recommend *not* running the groovy tests.  They set the groovy
> dependency to test scope which means groovy ends up not supported in
> the convenience binary.
> # Verify the build works including release audit tool (RAT) checks
>   cd nifi-0.5.0
>   mvn clean install -Pcontrib-check
> We should work to get the groovy stuff into the build without needing
> profile activation if they should be the norm.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message