[jira] [Closed] (MANTTASKS-186) MAVEN_OPTS environment variable isn't taken into account.

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MANTTASKS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MANTTASKS-186.
------------------------------------
    Resolution: Won't Fix

This component has been retired.

> MAVEN_OPTS environment variable isn't taken into account.
> ---------------------------------------------------------
>
>                 Key: MANTTASKS-186
>                 URL: https://issues.apache.org/jira/browse/MANTTASKS-186
>             Project: Maven Ant Tasks
>          Issue Type: New Feature
>          Components: mvn task
>    Affects Versions: 2.1.0
>            Reporter: Javier Murciego
>         Attachments: patch.diff
>
>
> I found that the are some differences between launch maven from command line or from maven-ant-task.  The pom task doesn't take into account the MAVEN_OPTS environment variable. 
> When the fork attribute is establised as false, maven-ant-task use ANT_OPTS environment variable. When fork is establised as true, no system properties are passed to jvm. It's posible set parameters using jvmarg nested element, but It would be nice that the maven-ant-task use MAVEN_OPTS automatically.
> I send as an attachment a patch (based on 2.1.0 version) adding this feature. The patch includes a new optional attribute for mvn task named useMavenOpts. If useMavenOpts is established true and MAVEN_OPTS exists, it will be added in the final maven call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)