[
https://issues.apache.org/jira/browse/AMBARI-21735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130186#comment-16130186
]
Hadoop QA commented on AMBARI-21735:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12882249/AMBARI-21735.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12007//console
This message is automatically generated.
> 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)
