You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Javi M (JIRA)" <ji...@codehaus.org> on 2010/06/01 20:44:12 UTC

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

MAVEN_OPTS environment variable isn't taken into account.
---------------------------------------------------------

                 Key: MANTTASKS-186
                 URL: http://jira.codehaus.org/browse/MANTTASKS-186
             Project: Maven 2.x Ant Tasks
          Issue Type: New Feature
          Components: mvn task
    Affects Versions: 2.1.0
            Reporter: Javi M
         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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira