[ https://jira.codehaus.org/browse/MNG-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339932#comment-339932 ]
Jason van Zyl commented on MNG-5199: ------------------------------------ So this is primarily a deficiency in the way options are passed on spawned execution environments. So if the -s parameter was passed on properly this would not be an issue yes? > Return back org.apache.maven.user-settings and > org.apache.maven.global-settings properties > ------------------------------------------------------------------------------------------ > > Key: MNG-5199 > URL: https://jira.codehaus.org/browse/MNG-5199 > Project: Maven 2 & 3 > Issue Type: New Feature > Components: Settings > Affects Versions: 3.0.3 > Reporter: Karel Piwko > > According to discussion at > http://maven.40175.n5.nabble.com/Maven-3-support-for-org-apache-maven-user-settings-td3261146.html, > I'm sure there is a valid use case for the property: > Imagine following: > {code} > mvn -s setting.xml test > {code} > Surefire has no way how to pass the path of the settings.xml in the spawned > process. If the test in spawned process want to for example access remote > repository defined in settings.xml, user has to specify settings.xml path in > the test itself. > However, for the following: > {code} > mvn -Dorg.apache.maven.user-settings=settings.xml test > {code} > This system property can be passed to surefire configuration and propagated > to the Surefire spawned process later on. > Having a system property removes duplication of the environment settings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira