[
https://issues.apache.org/jira/browse/MJAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAR-117.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> addClasspath should choosing scope
> ----------------------------------
>
> Key: MJAR-117
> URL: https://issues.apache.org/jira/browse/MJAR-117
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
