[
http://jira.codehaus.org/browse/SUREFIRE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221256#action_221256
]
Paul Gier commented on SUREFIRE-619:
------------------------------------
Just for some additional information, the current surefire classpath is
retrieved from MavenProject which basically just returns the paths to all of
the dependencies and the classes and test-classes directory. This requires
some hacky logic to fix the paths in the case that the user set a non default
location for the classes or test-classes directory in the surefire config.
What I'm trying to do with this issue is figure out a more elegant solution to
build the surefire classpath and still allow flexibility for the user to modify
this path to fit the needs of the project.
> 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
