[
https://jira.codehaus.org/browse/SUREFIRE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283408#comment-283408
]
Karel Piwko commented on SUREFIRE-790:
--------------------------------------
My specific use case is using Maven together with Arquillian for testing Java
EE applications.
Arquillian is building the test archive using Java programmatic API
(ShrinkWrap), e.g. creating a minimal archive required to reproduce a bug/test
a feature. This allows tests to be run much faster and from IDE without any
boostrap steps needed.
However, it might happen that user have to include a jar file in the test
archive. In that case, Aether is used via an ShrinkWrap extension. Aether has
no information that Surefire plugin started it, so pom.xml and settings.xml
have to be specified once again in the test itself.
This leads to:
1/ The information is duplicated
2/ If user activates a profile or pass different settings.xml file, it expects
that they will be passed to the test as well.
The key here is to be reproducible in both IDE and CLI. We can't simply move to
e.g. integration-test where we can expect dependencies are already resolved
somewhere in target/directory as this is not the way how neither of the IDEs
work.
The idea here is to be at least able to access path to settings.xml, pom.xml
and activated profiles, so it would be easy to reproduce the same environment
in "test Aether", no reason to make whole MavenSession serializable although
that we be nice.
How does this sound to you?
> 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
