[
https://jira.codehaus.org/browse/MCHRONOS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly moved MOJO-1679 to MCHRONOS-22:
------------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: chronos)
Affects Version/s: (was: chronos-maven-plugin-1.0-SNAPSHOT)
Key: MCHRONOS-22 (was: MOJO-1679)
Project: Mojo's Chronos Maven Plugins (was: Mojo)
> Chronos Jmeter goal doesn't resolve dependencies
> ------------------------------------------------
>
> Key: MCHRONOS-22
> URL: https://jira.codehaus.org/browse/MCHRONOS-22
> Project: Mojo's Chronos Maven Plugins
> Issue Type: Improvement
> Environment: Windows 7, Maven 3.0.3
> Reporter: Daniel Hopper
> Assignee: Kent Sølvsten
>
> It seems that the JMeterTestMojo isn't resolving all the necessary
> dependencies when you are attempting to run the goal.
> Especially if you are running JUnit test cases that may have dependencies on
> other libraries they are not properly found.
> I believe this can easily be resolved by added
> @requiresDependencyResolution test
> To the JMeterTestMojo class that way all the project dependencies can be
> copied to the jmeter/lib/junit directory (similarly to the JMeterGuiMojo)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
