[
http://jira.codehaus.org/browse/MFITNESSE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117298
]
pkernevez commented on MFITNESSE-18:
------------------------------------
This is not by design, rather by context. In our project we separated the
reports and the fixtures, and I never tried to do that.
I will integrate the functionality and surely your path.
> Fixtures classes from the project sources or test-sources are not included in
> classpath
> ---------------------------------------------------------------------------------------
>
> Key: MFITNESSE-18
> URL: http://jira.codehaus.org/browse/MFITNESSE-18
> Project: Maven 2.x Fitnesse Plugin
> Issue Type: Bug
> Affects Versions: 1.0-beta-1, 1.0-beta-2
> Environment: Win32 (XP)/JDK6.1
> Reporter: Adi
> Assignee: pkernevez
> Attachments: FitnesseRunnerMojo.java.patch
>
>
> When using classPathProvider=maven, the fitnesse runner commandline generated
> by the plugin does not specify targe/classes or target/test-classes as part
> of the classpath. Hence any fixture classes defined in the project are not
> included when executing.
> Not sure if this is by design. I have a patch that does include these
> artifacts, attached to this issue.
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
