[
https://jira.codehaus.org/browse/SUREFIRE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283397#comment-283397
]
Kristian Rosenvold commented on SUREFIRE-790:
---------------------------------------------
Can you give a clearer indication as to why a test should need to be resolving
dependencies on its own ? Some specific use cases seem to be in order, since
this issue on first looks seems like a clear "wont' fix" to me.
> Allow forked process to access the Maven session of parent
> ----------------------------------------------------------
>
> Key: SUREFIRE-790
> URL: https://jira.codehaus.org/browse/SUREFIRE-790
> Project: Maven Surefire
> Issue Type: New Feature
> Components: process forking
> Affects Versions: 2.10
> Reporter: Karel Piwko
>
> Forked process should be able to get information from a "parent process",
> which is a Maven build execution.
> This will allow the test to access information like which pom.xml file being
> processed, settings.xml and Maven Reactor plugin.
> This feature is needed to any test which want to interfere with Maven
> repositories with Aether, for instance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
