You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/11/22 10:44:00 UTC
[jira] [Updated] (FLINK-24984) Rename MAVEN_OPTS variable in azure yaml
[ https://issues.apache.org/jira/browse/FLINK-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-24984:
-----------------------------------
Labels: pull-request-available (was: )
> Rename MAVEN_OPTS variable in azure yaml
> ----------------------------------------
>
> Key: FLINK-24984
> URL: https://issues.apache.org/jira/browse/FLINK-24984
> Project: Flink
> Issue Type: Sub-task
> Components: Build System / Azure Pipelines
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The build-apache-repo.ymnl defines a MAVEN_OPTS variable, which are later passed to Maven.
> This is a bit misleading because MAVEN_OPTS already has semantics attached to it by Maven itself, in that it passes the value of such an environment variable to the JVM.
> As such it can, and should, only be used to control JVM parameters (e.g., memory), and not Maven-specific stuff. In fact the JVM would fail if, for example, it were to contain a profile activation.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)