[
http://jira.codehaus.org/browse/SUREFIRE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221255#action_221255
]
Paul Gier commented on SUREFIRE-619:
------------------------------------
There are some use cases defined in the two linked issues. More complete
control over the classpath is useful any time you want to run tests against
multiple dependency configurations. The recommendation I've heard in the past
is to use multiple separate test projects (POMs) which depend on the project
you are testing, but this can be difficult because of SUREFIRE-569.
> The surefire plugin should generate it's own classpath
> ------------------------------------------------------
>
> Key: SUREFIRE-619
> URL: http://jira.codehaus.org/browse/SUREFIRE-619
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading, Maven Surefire Plugin
> Affects Versions: 2.5
> Reporter: Paul Gier
> Assignee: Paul Gier
> Fix For: 2.6
>
>
> I believe the surefire plugin would be improved if it generated it's own
> classpath instead of getting the test classpath from MavenProject. This
> would allow the user better control over what is included in the classpath,
> and would actually simplify parts of the code for building the classpath.
> The risk associated with this change is that the default surefire classpath
> could end up being different than the test classpath in MavenProject.
> However, I think that as long as the surefire plugin classpath generation is
> well documented, this won't cause a problem for users.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
