You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/11/22 12:25:00 UTC
[jira] [Commented] (NIFI-10849) Change GitHub Maven Compile Step to run test-compile
[ https://issues.apache.org/jira/browse/NIFI-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637228#comment-17637228 ]
ASF subversion and git services commented on NIFI-10849:
--------------------------------------------------------
Commit 4725ca36badd2cb9e11afda2bb3643a7bfb4cab6 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4725ca36ba ]
NIFI-10849 Changed Maven compile to test-compile in GitHub ci-workflow
Signed-off-by: Pierre Villard <pi...@gmail.com>
This closes #6691.
> Change GitHub Maven Compile Step to run test-compile
> ----------------------------------------------------
>
> Key: NIFI-10849
> URL: https://issues.apache.org/jira/browse/NIFI-10849
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The GitHub ci-workflow runs separate Maven commands for compilation and verification to differentiate compile and test operations. The Maven Compile step should be changed from {{compile}} to {{test-compile}} in order to compile both standard and test classes. The Maven Compile runs with multiple threads for increased performance on runners with multiple cores, so changing the command to {{test-compile}} provides some small performance gains.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)