You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 00:51:22 UTC

[jira] Updated: (MNG-942) Ability to source system properties in settings.xml

     [ http://jira.codehaus.org/browse/MNG-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-942:
-----------------------------

    Fix Version/s:     (was: 2.1)

> Ability to source system properties in settings.xml
> ---------------------------------------------------
>
>                 Key: MNG-942
>                 URL: http://jira.codehaus.org/browse/MNG-942
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0-beta-1
>         Environment: Maven 2.0-beta-1
> WIN XP PRO SP2
> java version "1.5.0_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
>            Reporter: John Allen
>            Assignee: John Casey
>            Priority: Trivial
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Would be nice to be able to source Java System properties in the global and user settings.xml file. This is intended to allow custom build systems to set arbitrary m2 settings.xml properties programmatically by wrapping m2 executable in their own wrapper exe and then passing these settings to M2 via the JVM options ($MAVEN_OPTS). Currently only explicitly supported settings can be overrided/defined by system properties (such as maven.repo.local).
> An example might be the proxy being employed, depending on where the build is being run from the proxy might be set differently. Note the same machine is being used (a laptop in this case) but operates in multiple locations and therefore network configurations (work/home). The M2 wrapping script can detect this difference from network info (ipconfig or IE connection details) and set the proxy details appropriately. I guess in this example it would be even better if it was just able to set a System property that acted as a switch which then activated the correct proxy configuration defined in settings.xml.

-- 
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