[
https://issues.apache.org/jira/browse/SUREFIRE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905934#comment-14905934
]
ASF GitHub Bot commented on SUREFIRE-790:
-----------------------------------------
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/2#issuecomment-142837160
Enabled by default would mean to introduce a new feature and new bugs and
requirements in Jira.
The reason why we want the users to implement the API in their own is to
get freedom in Jira and solve contradictory issues.
It's pragmatic decision from our side. I understand that users would prefer
us to implement but we have limited resources.
On Thu, Sep 24, 2015 at 8:53 AM, Karel Piwko <[email protected]>
wrote:
> @Tibor17 <https://github.com/Tibor17> SPI would work for me. Basically
> any means how to get the information about Maven process to forked JVM
> would be helpful, if enabled by default, even better.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/maven-surefire/pull/2#issuecomment-142831231>.
>
--
Cheers
Tibor
> 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)
