You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2017/09/19 10:43:01 UTC
[jira] [Commented] (AMBARI-21735) Parameterize Maven Surefire Build
argLine
[ https://issues.apache.org/jira/browse/AMBARI-21735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171497#comment-16171497 ]
Dmitry Lysnichenko commented on AMBARI-21735:
---------------------------------------------
[~jonathan.hurley],
Looks like DDLs has been updated, but upgrade catalogs stay intact. Is that desired?
> Parameterize Maven Surefire Build argLine
> -----------------------------------------
>
> Key: AMBARI-21735
> URL: https://issues.apache.org/jira/browse/AMBARI-21735
> Project: Ambari
> Issue Type: Task
> Affects Versions: 2.6.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.6.0
>
> Attachments: AMBARI-21735.patch
>
>
> Regardless of what options are set via {{MAVEN_OPTS}} or even {{-DargLine=...}}, the surefire plugin seems to force the hard coded arg lines for forked VMs:
> {code}
> /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre/bin/java -Xms512m -Xmx1024m -jar
> {code}
> Setting argLines to different values is never picked up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)