[
https://issues.apache.org/jira/browse/NIFI-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191107#comment-15191107
]
ASF subversion and git services commented on NIFI-1511:
-------------------------------------------------------
Commit f6705f234cd527c2bc0edd670854f2947277f3f5 in nifi's branch
refs/heads/master from [~joewitt]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f6705f2 ]
NIFI-1511 we now ensure groovy eclipse compiler is only used during testCompile
goal
This closes #270
Signed-off-by: Matt Burgess <[email protected]>
> 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)
