[
https://jira.codehaus.org/browse/SUREFIRE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283486#comment-283486
]
Karel Piwko commented on SUREFIRE-790:
--------------------------------------
Writing a specific plugin does not really help here, because the test itself is
responsible for the packaging.
If we move this responsibility to the plugin, we would have an intermediate
step. This means that we can't update the test from the IDE on-the-fly, we have
to store the step result somewhere on the filesystem, etc., making test
development much more difficult.
Plugin would not be able to build multiple packages, specific packages per
container, etc., basically it will loose all advanced Arquillian features.
> 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
