[
https://jira.codehaus.org/browse/SUREFIRE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283419#comment-283419
]
Kristian Rosenvold commented on SUREFIRE-790:
---------------------------------------------
It also sounds like you should be writing a "arquillian-maven-plugin" that does
the ShrinkWrapping, artifact resolution and project modification /prior/ to
invoking surefire in a regular fork.
Generalized access to the "session" within the forked process is just /not/
going to happen if I understand anything at all; something aether specific
*maybe*. The fork is designed to stay minimalistic and "clean" and this
suggestion certainly breaks that constraint totally.
> 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
