[ http://jira.codehaus.org/browse/MJAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tuomas Kiviaho updated MJAR-117: -------------------------------- Attachment: pom.xml If I understood correctly you're having similar problem as I have. Dependencies are not included into manifest classpath when their scope is test. There is one dependency with transitivity in the attached IT pom that I expected to be included into manifest classpath of test-jar as Class-Path: junit-dep-4.4.jar hamcrest-core-1.1.jar > addClasspath should choosing scope > ---------------------------------- > > Key: MJAR-117 > URL: http://jira.codehaus.org/browse/MJAR-117 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement > Environment: mvn 2.0.9, > Reporter: Kamil Demecki > Attachments: pom.xml > > > We have project to running tests for system. Running single test from "mvn > test" works. The problem is that sometimes part of this project is using > standalone from command line. So zip is builded from "mvn assembly" with > scope "test" but dependencies "test" are not added to jar Manifest with > option "addClasspath". > Is possible to add additional argument "addClasspathScope" which should > resolve situation? > Other solution is to change scope for dependencies for this project, but it > not so simple, because our configuration looks: > project-01 > main > test > project-02 > main > test > ... > project-100 > main > test > project-integration-tests > main > Projects [01-100] have "scope test" dependendencies and > project-integration-tests inherit this "scope test" dependendencies. To > choose solution (2), pom for project-integration-tests should override all > test dependendencies with scope "compile". -- 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