[
https://issues.apache.org/jira/browse/SUREFIRE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905431#comment-14905431
]
ASF GitHub Bot commented on SUREFIRE-790:
-----------------------------------------
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/2#issuecomment-142749714
@kpiwko
@gastaldi
@marcusholl
What can we do about this old issue?
My suggestion is to propose SPI in Surefire 3.x where hacking system
properties in forked jvm would be fetched right from plugin process.
I want to have groovy scripting with interfaces in Surefire API instead of
SPI.
> Allow forked process to access the Maven session of parent
> ----------------------------------------------------------
>
> Key: SUREFIRE-790
> URL: https://issues.apache.org/jira/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 was sent by Atlassian JIRA
(v6.3.4#6332)
