[
https://issues.apache.org/jira/browse/NIFI-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191063#comment-15191063
]
ASF GitHub Bot commented on NIFI-1511:
--------------------------------------
GitHub user joewitt opened a pull request:
https://github.com/apache/nifi/pull/270
NIFI-1511 now only sets groovy eclipse compiler for test compiles
NIFI-1511 now only sets groovy eclipse compiler for test compiles
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/joewitt/incubator-nifi NIFI-1511
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/270.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 #270
----
commit aaee620dc858d83e92a32145e15548728c3c61c3
Author: joewitt <[email protected]>
Date: 2016-03-11T15:33:46Z
NIFI-1511 now only sets groovy eclipse compiler for test compiles
----
> 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)
