[ http://jira.codehaus.org/browse/MEV-254?page=comments#action_53138 ]
Joerg Schaible commented on MEV-254: ------------------------------------ Doesn't easymock extend JUnit ? Then the scope is perfect with compile. If *you* use easymock to test your app code, you must put easymock with scope "test" into your dependencies. This should change the scope for the transitive dep to junit also. > easymock 1.1 invalid scope for junit > ------------------------------------ > > Key: MEV-254 > URL: http://jira.codehaus.org/browse/MEV-254 > Project: Maven Evangelism > Type: Improvement > Components: Dependencies > Reporter: Jean-Laurent de Morlhon > > > easymock 1.1 provides a default compile scope for JUnit but it should be > <scope>test</scope> > http://www.ibiblio.org/maven2/easymock/easymock/1.1/easymock-1.1.pom > workaround: > add <scope>test</scope> to the JUnit dependencies in your local repository -- 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, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
