You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhilong Hong (Jira)" <ji...@apache.org> on 2021/02/09 11:24:00 UTC
[jira] [Commented] (FLINK-21335) README should use "mvn install"
instead of "mvn package" to compile Flink
[ https://issues.apache.org/jira/browse/FLINK-21335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281718#comment-17281718 ]
Zhilong Hong commented on FLINK-21335:
--------------------------------------
In fact I always use {{mvn package}}, rather than {{mvn install}}. Put the compiled Flink into local maven repository is not necessary when you compile the Flink.
> README should use "mvn install" instead of "mvn package" to compile Flink
> -------------------------------------------------------------------------
>
> Key: FLINK-21335
> URL: https://issues.apache.org/jira/browse/FLINK-21335
> Project: Flink
> Issue Type: Improvement
> Reporter: Dong Lin
> Priority: Minor
>
> Currently README suggests users to use "mvn package" to build Flink. As a result, the compiled package will not be put in mvn local repository, and "mvn test" will download/use snapshots from remote repository instead of testing local code change.
> This is a bit unintuitive since developers (including those who are not so familiar with maven's mechanism) in general expect "mvn test" to test local code changes.
> So it seems better to update README to use "mvn install" instead of "mvn package". There is no downside of this change to my best knowledge.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)